Yeah! Routing in the next lesson!... I'm soo excited as I would like to see if laravel could really boost my project's routing. I wonder if you already will include the whole middleware into that video or will ignore that for the moment 🙂 I am still not 100% convinced to use laravel for future projects. Indeed your great teaching enables me to more likely think about own adequate solutions where laravel gives me extra convenience to reach even better convenience for me.
Hie sir sorry to ask you this is it appropriate to use Github as a link to my portfolio Projects on my cv when applying for a Job,because I cannot find a free hosting service
great stuff again! @ 5:37 you mention that we can pass an array. As I learned from you in PHP course 'PHP Function Parameters' we have a variadic method environment() here that uses the splat operator. So passing just the elements without wrapping it into '[' and ']' should work just fine, no? Or did something change since the 3 year old video? Another thing I wonder about is, that laravel - not only in this case - avoids typehinting. Would you consider this as a weakness of laravel or even a strength? Does it make sense in the context of framework?
Hey, we have the same idea in the previous course learn PHP the right way 'type hinting' is introduce but in this case in using laravel maybe the mapping of each type is improve but not means that type hinting is not useful in the framework it depends in certain use cases where we need to ensure that we need to pass the exact type to avoid errors. vanilla php is less powerful than laravel, there are also a extension in VSCode which can know how to type hint maybe from "PHP Intelephense" or "PHP Devsense".
@@happyfriendsentertainment ya, for me its hard to decide for my own opinion on that. On the one hand it absolutely makes sense to typehint and to "stricten" the own code as this enhances readability and eases the debugging a lot. On the other hand I think this is - and I know 99% of all programmers will not agree - also a big strength in PHP and other "loose" program languages. As long as we - the programmers - know what we do*, we are able to use solutions that go beyond the possibilities of strict patterns. In many languages it wouldn't be possible to rewrite its own code during runtime. In PHP it is. Factory/Write a new class file, autoload it during runtime. Programmers wonderland for the one, horror for those who want to find out what the code will do tomorrow. I think the most important is to use strict pattern where possible and to really know where and why to break these chains. And this is why I think Gio's decision for the "environment" of financial transactions for his tutorials is well decided. Everyone is clear about the fact that we want to exactly know what this code does with our money tomorrow - no chance for loosening. Other topics nowadays might need some let go on the own code to bring magic to it. *in fact that is the key as well for the opposite opinion - all programmers working on one project know much better what all together do, when they speak the same language/strict patterns/framework. The reason for my own dilemma 🙂 @happyfriendsentertainment What you mention, that laravel is more powerful than vanilla php... thats what I really search for. At least laravel is made out of php. I know that in general it makes no sense to reinvent the wheel. But as I am not bound to the need of fast progress or timelines as a professional programmer usually is, I go through Gio's great tutorials to find out what magic I need from laravel and what magic I might be able to create or even enhance on my own. The biggest power of all third party elements of your code is always if they are battle tested by many people. But in my opinion, if you as a programmer do something really new with the "foreign" code, this strength is only valid, if you use the code the right way. Therefore its needed to learn what the "foreign" code does the right way. That brings me to the result, that I at least can decide, if the result of what I at the end want to achieve becomes better if I adjust my own coding the right way to what a framework, like laravel needs or if I change/create what laravel does so that it is the right way for my code*. *may I apply for record "the longest and most weird sentence"? I hope its understandable 🤣 At the end I think it is as always, everything depends... 🙂
About typehinting, it really depends. Don't forget Laravel was developed awhile ago, its not a new framework. They are constantly improving it & are adding types in newer versions. Adding types everywhere now would introduce a lot of breaking changes and Laravel is trying to minimize breaking changes to make upgrading from one version to the next as easy as possible.
@@ProgramWithGio ah! It's always great to have someone experienced like you to explain these (for me) unlogical/confusing features! Thank you for always taking your time for such incredible answers!!!
hello, Gio i appreciate your work thank you i will my lecture. if i can ask how to modify my laravel 9 code to 11.34 for file like app/http/kernel.php not available in laravel 11 how to solve it if i can get a tutorial i will appreciate.
Follow the upgrade guide from 9 to 10, then from 10 to 11. You dont need to have the same structure as fresh Laravel 11, its backward compatible so it should work with old structure as well. If your app is small enough then you can just start a fresh Laravel 11 and port your models/classes over but if its too much effort just go with the upgrade
Great! I never even thought that I could add my own config file. Thanks a lot Gio. On to the next
Can be pretty useful
Thanks, Gio,
Remarkably informative
Through all my channels, I'm just looking forward to see your channel's notification.❤
Awesome! Thank you! 💙💙
This course is made out of love and will help a tonne of people❤
Hope so 🙏
I found the caching part is extremely helpful, thanks!
Glad to hear it!
I like it, it's very informative.
Thanks Gio!
Glad you like it, thank you 💙
Great, Thanks Gio
Thank you 🙏
Thanks, Gio,
Clear explanation.
Glad it was helpful! 🙌
Yeah! Routing in the next lesson!... I'm soo excited as I would like to see if laravel could really boost my project's routing. I wonder if you already will include the whole middleware into that video or will ignore that for the moment 🙂 I am still not 100% convinced to use laravel for future projects. Indeed your great teaching enables me to more likely think about own adequate solutions where laravel gives me extra convenience to reach even better convenience for me.
💙💙
Hie sir sorry to ask you this is it appropriate to use Github as a link to my portfolio Projects on my cv when applying for a Job,because I cannot find a free hosting service
Yea it's totally fine
The Man. The tutorial...
💙💙
great stuff again!
@ 5:37 you mention that we can pass an array. As I learned from you in PHP course 'PHP Function Parameters' we have a variadic method environment() here that uses the splat operator. So passing just the elements without wrapping it into '[' and ']' should work just fine, no? Or did something change since the 3 year old video?
Another thing I wonder about is, that laravel - not only in this case - avoids typehinting. Would you consider this as a weakness of laravel or even a strength? Does it make sense in the context of framework?
Hey, we have the same idea in the previous course learn PHP the right way 'type hinting' is introduce but in this case in using laravel maybe the mapping of each type is improve but not means that type hinting is not useful in the framework it depends in certain use cases where we need to ensure that we need to pass the exact type to avoid errors. vanilla php is less powerful than laravel, there are also a extension in VSCode which can know how to type hint maybe from "PHP Intelephense" or "PHP Devsense".
@@happyfriendsentertainment ya, for me its hard to decide for my own opinion on that. On the one hand it absolutely makes sense to typehint and to "stricten" the own code as this enhances readability and eases the debugging a lot. On the other hand I think this is - and I know 99% of all programmers will not agree - also a big strength in PHP and other "loose" program languages. As long as we - the programmers - know what we do*, we are able to use solutions that go beyond the possibilities of strict patterns. In many languages it wouldn't be possible to rewrite its own code during runtime. In PHP it is. Factory/Write a new class file, autoload it during runtime. Programmers wonderland for the one, horror for those who want to find out what the code will do tomorrow. I think the most important is to use strict pattern where possible and to really know where and why to break these chains. And this is why I think Gio's decision for the "environment" of financial transactions for his tutorials is well decided. Everyone is clear about the fact that we want to exactly know what this code does with our money tomorrow - no chance for loosening. Other topics nowadays might need some let go on the own code to bring magic to it.
*in fact that is the key as well for the opposite opinion - all programmers working on one project know much better what all together do, when they speak the same language/strict patterns/framework. The reason for my own dilemma 🙂
@happyfriendsentertainment What you mention, that laravel is more powerful than vanilla php... thats what I really search for. At least laravel is made out of php. I know that in general it makes no sense to reinvent the wheel. But as I am not bound to the need of fast progress or timelines as a professional programmer usually is, I go through Gio's great tutorials to find out what magic I need from laravel and what magic I might be able to create or even enhance on my own. The biggest power of all third party elements of your code is always if they are battle tested by many people. But in my opinion, if you as a programmer do something really new with the "foreign" code, this strength is only valid, if you use the code the right way. Therefore its needed to learn what the "foreign" code does the right way. That brings me to the result, that I at least can decide, if the result of what I at the end want to achieve becomes better if I adjust my own coding the right way to what a framework, like laravel needs or if I change/create what laravel does so that it is the right way for my code*.
*may I apply for record "the longest and most weird sentence"? I hope its understandable 🤣
At the end I think it is as always, everything depends... 🙂
Yes you can pass it as multiple arguments instead of an array. Documentation uses array so I decided to use array as well to avoid confusion.
About typehinting, it really depends. Don't forget Laravel was developed awhile ago, its not a new framework. They are constantly improving it & are adding types in newer versions. Adding types everywhere now would introduce a lot of breaking changes and Laravel is trying to minimize breaking changes to make upgrading from one version to the next as easy as possible.
@@ProgramWithGio ah! It's always great to have someone experienced like you to explain these (for me) unlogical/confusing features! Thank you for always taking your time for such incredible answers!!!
👏👏
💙💙
hello, Gio i appreciate your work thank you i will my lecture. if i can ask how to modify my laravel 9 code to 11.34 for file like app/http/kernel.php not available in laravel 11 how to solve it if i can get a tutorial i will appreciate.
Follow the upgrade guide from 9 to 10, then from 10 to 11. You dont need to have the same structure as fresh Laravel 11, its backward compatible so it should work with old structure as well. If your app is small enough then you can just start a fresh Laravel 11 and port your models/classes over but if its too much effort just go with the upgrade