Absolutely brilliant dive into the Laravel architecture! Well explained content, I am very glad that I found Gio materials, as he does tremendous job. Contgrats to the author of this channel!
It's so exciting slowly tip-toeing into Laravel like this. I really loved how detailed but clear your whole PHP course was, I can't wait to get into every little detail of Laravel in the same way. Thank you so much for doing this!
Hi Gio, so when I looked into Laravel myself earlier, I was totally intimidated by all these things. I tried to figure them out but dropped out at some point. Thank you for taking us through this. I absolutely want to understand it more. I kept pausing the lesson, and I need to watch it again
Exciting, been following you since the php series. I also appreciate you slowing down when explaining, to me the tempo is much better now. Kudos to you man, looking forward to the next videos.
Wow! Great stuff! Thats exactly what I did after I installed laravel and before I started to insert any code. But for sure I did not understand 10% of what I understood with your guided tour! Thanks Gio! There are still some points that make me wonder. Some feel for me like 'unneccessary' duplicated code others just feel weird. I understand why you program a function or method with the only task to forward a request in a project but in a 'ready' to use framework it makes no real sense to me. Is it meant to serve an entry point for the framework user to include own middleware extensions in these cases? I find such examples all through laravel. My only idea was that it might include an extra portion of security but I hope you will explain this later in this series 🙂 I'm so excited to follow the next 100 parts of the series!
@@ProgramWithGio no, with routers there are usually many 'forwardings' and that makes sense as you delegate the routing to a class. What I meant are such things like @ 4:22 Inside a class the one method calls: $this->bootstrappers() and then you have the bootstrappers method that has the heavy weight and only duty to: return $this->bootstrappers; Why not just access the argument directly from the method bootstrap()? In my naive brain there would not really be a benefit as you are inside the same class, is there? Does it make a difference to call a protected method or use a protected argument? #confusesme 😆
It would be a great exercise to draw this diagram to be honest. What I've explained in the video and shown the process can easily be translated into diagram. Give it a try, it will make more sense & is good practice
Hi Gio, Thanks for this great video. I'm woundering why the Application class extends the Container class ?, wouldn't the composition choice here make more sense ? I can't figure out if the Application and Container relation is a (is -> a) relation. Another thing, I was woundering why the Application class is not a Singelton class ?, but when you mentioned the console I've figured out that we might have 2 instances of the Application class created within the same time (one for Http requests and the other for console commands).
I dont know the reasoning behind such decisions but Taylor is a lot smarter than me so I trust his reasoning along with his team. Application is kind of a service container, it basically implies that the application is essentially a specialized version of a container. Laravel can easily integrate the service container functionality throughout the framework without needing to duplicate code or add more layers of abstraction. If instead of inheritance, Application had a Container as a property (composition), then you would need to manage this container separately. This could create more complexity because you'd be delegating container behavior to another class. Would this be a better approach? Honestly, it depends on what the goal was, if Application is meant to be a service container then its fine using inheritance.
Hello Gio . I hope you do well. The Kernal.php File in Laravel 11 is not exist anymore , what is the alternative of it .? For the middleware i use the bootstrap/app.php .
Спасибо. Я из России. Мне очень нравится, как вы обьясняете. Программирование я не понимаю, но хочется понять. Еще мечтаю учить Английский язык. А у вас все сразу, и Английский и программирование. Я только начала изучать тестирование. Для меня это волшебство.@@ProgramWithGio
Absolutely brilliant dive into the Laravel architecture! Well explained content, I am very glad that I found Gio materials, as he does tremendous job. Contgrats to the author of this channel!
Thank you & glad you are here 💙
It's so exciting slowly tip-toeing into Laravel like this. I really loved how detailed but clear your whole PHP course was, I can't wait to get into every little detail of Laravel in the same way. Thank you so much for doing this!
Glad it was helpful! Thank you 💙
Hi Gio, so when I looked into Laravel myself earlier, I was totally intimidated by all these things. I tried to figure them out but dropped out at some point. Thank you for taking us through this. I absolutely want to understand it more. I kept pausing the lesson, and I need to watch it again
Yup, can take some time to fully grasp it
so exciting on diving into Laravel like this. nowhere found this level clear and detail explanation
Glad you like it
Probably the easiest Request Life Cycle Video I have ever seen though the new directory has simplified it a lot
💙💙
Exciting, been following you since the php series. I also appreciate you slowing down when explaining, to me the tempo is much better now. Kudos to you man, looking forward to the next videos.
Happy to hear that, thank you 💙💙
Gio is the best, period.
💙💙
I like the pace of this series.
Thanks Gio!
💙💙
Very well done. This demystifies The magic a lot.
Happy to hear, thank you
This is so so good!
Thank you
Great Explanation! This is true knowledge.
Glad it was helpful 💙
The best teacher 🎉
💙💙
Great video quality! Thank You!
Thank you
What a perfect start...
Thank you
Man you are awesome.love from Pakistan
No, you're awesome 🙌
Thank you so much for lessons
💙💙
Great start, thank you!
You're welcome!
Wow! Great stuff! Thats exactly what I did after I installed laravel and before I started to insert any code. But for sure I did not understand 10% of what I understood with your guided tour! Thanks Gio! There are still some points that make me wonder. Some feel for me like 'unneccessary' duplicated code others just feel weird.
I understand why you program a function or method with the only task to forward a request in a project but in a 'ready' to use framework it makes no real sense to me. Is it meant to serve an entry point for the framework user to include own middleware extensions in these cases? I find such examples all through laravel. My only idea was that it might include an extra portion of security but I hope you will explain this later in this series 🙂 I'm so excited to follow the next 100 parts of the series!
Thank you. If you are referring to a router yes its meant to direct the traffic to the right action. Better separation of concerns.
@@ProgramWithGio no, with routers there are usually many 'forwardings' and that makes sense as you delegate the routing to a class.
What I meant are such things like @ 4:22
Inside a class the one method calls:
$this->bootstrappers()
and then you have the bootstrappers method that has the heavy weight and only duty to:
return $this->bootstrappers;
Why not just access the argument directly from the method bootstrap()? In my naive brain there would not really be a benefit as you are inside the same class, is there?
Does it make a difference to call a protected method or use a protected argument?
#confusesme 😆
Is there a diagram by any chance that shows the whole process of calls and the paths you showed? Thanks so much for your videos tho 🙏🤓
It would be a great exercise to draw this diagram to be honest. What I've explained in the video and shown the process can easily be translated into diagram. Give it a try, it will make more sense & is good practice
Just Just And Just Love it.. what an explanation. Awesome. do u have any service provider and container specific content or video brother?
Yes, a bit later
Hi Gio, Thanks for this great video.
I'm woundering why the Application class extends the Container class ?, wouldn't the composition choice here make more sense ?
I can't figure out if the Application and Container relation is a (is -> a) relation.
Another thing, I was woundering why the Application class is not a Singelton class ?, but when you mentioned the console I've figured out that we might have 2 instances of the Application class created within the same time (one for Http requests and the other for console commands).
I dont know the reasoning behind such decisions but Taylor is a lot smarter than me so I trust his reasoning along with his team. Application is kind of a service container, it basically implies that the application is essentially a specialized version of a container. Laravel can easily integrate the service container functionality throughout the framework without needing to duplicate code or add more layers of abstraction.
If instead of inheritance, Application had a Container as a property (composition), then you would need to manage this container separately. This could create more complexity because you'd be delegating container behavior to another class. Would this be a better approach? Honestly, it depends on what the goal was, if Application is meant to be a service container then its fine using inheritance.
Keep Going 🥰
Always
thanks man
💙💙
Thanks man
You're welcome
❤❤
💙💙
❤
💙
thank you for the reassurance but I still feel I need to review PHP the right way here and there😅
And that's ok, if you feel like you have a gap or something doesnt make sense, refer back to PHP series. It can work
Hello Gio . I hope you do well.
The Kernal.php File in Laravel 11 is not exist anymore , what is the alternative of it .?
For the middleware i use the bootstrap/app.php .
The Kernel.php file still exists but is no longer published directly in your project’s directory by default, as it was in previous versions.
yes like @karamm3353 mentioned its within vendor as shown & explained in the video
Great
Thank you
i am still trying to understand...
Feel free to ask questions. It can take some time to fully grasp it
i mean the video is amazing but you gotta breathe a little bit of air you're talking too fast 😂
Honestly this is as slow as I can go. I cant talk any slower, it's just the way I talk to be honest 😂
@@ProgramWithGio I actually binge on your PHP series BECAUSE of the way you talk, love it. Thanks for all this great work 🙏
Спасибо. Я из России. Мне очень нравится, как вы обьясняете. Программирование я не понимаю, но хочется понять. Еще мечтаю учить Английский язык. А у вас все сразу, и Английский и программирование. Я только начала изучать тестирование. Для меня это волшебство.@@ProgramWithGio
dont cut the audio like that
what do u mean?