Nice insight into Laravel 11; I kind of like the new structure, especially since different projects often require different setups. It's great that you can adjust as necessary. One thing I noticed in the video around 8:25 is that SQLite is set as the standard database. While this might be convenient for some developers, it could be a bit annoying for PHP developers 🤔. Thanks for the video, really good.
Hey, thanks for the kind words great attention to detail. The default is SQLite, but at any given time inside the database.php file you can configure to this to whatever relational database management system you need as with previous Laravel frameworks. Thanks for watching.
It’s a custom theme with a cursive font. I know that does really help but it took me a while to tweak it just the way I like. Maybe I can put it out in the PHPStorm community.
This change is amazing for new people starting out with laravel. I am not a huge fan of this change really. My old issue is Taylor pushing sqlite, that's great for lightweight projects it sucks got large projects.
Thanks for the comment, you’re not just restricted to SQLite on this one. You may add other database engines that fit your requirements for projects you’re working on. I may provide more clarification on this one in a future video. Thanks for watching.
90% of what I know about how Laravel works came from browsing that "overwhelming" number of files in the default project. I'd be far more okay with this if 11 shipped with an artisan command to publish everything that used to be there by default.
I can understand that this can be overwhelming if your new or coming from different iteration of Laravel. Not sure if they have a "publish everything command" , but there are commands that will help you get to the parts of the framework that are used when necessary for your type of project. Hope this helps. Keep learning, and thanks for watching.
Great comment 👍, right now it’s not the smallest framework out there following the MVC pattern, however it’s relatively lightweight and few megabytes until you add vendor dependencies and packages. The expectation is the new changes will most likely help reduce overall footprint. 😀
Well, the verdict is still out on this one as it’s not released yet. Hopefully, you’ll be able to find some common ground with this upcoming update versus older versions of Laravel. Time will tell, thanks for the comment 😀
This update was inevitable, since, previously almost 70% of the files and code would not have been needed to develop most of the apps online, however, they were there by default and making the app slower to respond in competition to other frameworks. Now, after 11 we hope we will be importing and using what is only needed.
This is true depending on what you’re building. So you either have to refer to the documentation a little bit more or have knowledge of what was there before and reach for what you need. For example, replacing sqlite db with MySQL etc… in your .env file. Great comment.
Nice insight into Laravel 11; I kind of like the new structure, especially since different projects often require different setups. It's great that you can adjust as necessary. One thing I noticed in the video around 8:25 is that SQLite is set as the standard database. While this might be convenient for some developers, it could be a bit annoying for PHP developers 🤔. Thanks for the video, really good.
Hey, thanks for the kind words great attention to detail. The default is SQLite, but at any given time inside the database.php file you can configure to this to whatever relational database management system you need as with previous Laravel frameworks. Thanks for watching.
Love the way you explained. Thanks
Your welcome , my pleasure 😊
Thank so much for this update. The changes is paragime shift. Infact it will better if they strip it further. Just like react or express.
You’re welcome ☺️. It’s nice that they let you add what you need to your project when you need it.
I totally loved this, now it makes more sense, and less cluttered and intimidating 😂
I’m so glad it helped you out. Enjoy your day!
Thank you William, nice overview!
So glad you liked it, let me know if you would like to see future videos like this one😆👍
hmmmm so how can i register a middleware and things that previously was in the kernel.php
I'm surprised there are no comments on this video (yet). This was a great look at and comparison of L11, I definitely like the new slimmer style. 👍
Thank you for being the first. I’m glad you enjoyed it.
Man how to get those adding command because i want them for ex console and the exception
Thanks for your great explanation.
You bet! Glad you found it useful. Enjoy your weekend.
What is PHPstorm theme?
It’s a custom theme with a cursive font. I know that does really help but it took me a while to tweak it just the way I like. Maybe I can put it out in the PHPStorm community.
Yes please. I love it
This change is amazing for new people starting out with laravel.
I am not a huge fan of this change really.
My old issue is Taylor pushing sqlite, that's great for lightweight projects it sucks got large projects.
Thanks for the comment, you’re not just restricted to SQLite on this one. You may add other database engines that fit your requirements for projects you’re working on. I may provide more clarification on this one in a future video. Thanks for watching.
Thank you
You're welcome
90% of what I know about how Laravel works came from browsing that "overwhelming" number of files in the default project. I'd be far more okay with this if 11 shipped with an artisan command to publish everything that used to be there by default.
I can understand that this can be overwhelming if your new or coming from different iteration of Laravel. Not sure if they have a "publish everything command" , but there are commands that will help you get to the parts of the framework that are used when necessary for your type of project. Hope this helps. Keep learning, and thanks for watching.
Never break SOLID principle even the codebase is overwhelmed😂. It's time to think out of box for old php devs
i sure hope they add some kind of flag that won't force this slim version on us.
That's a lot ❤
😆 looking forward to the new update.
look lighter and smaller but inside is giant service container😂
Great comment 👍, right now it’s not the smallest framework out there following the MVC pattern, however it’s relatively lightweight and few megabytes until you add vendor dependencies and packages. The expectation is the new changes will most likely help reduce overall footprint. 😀
👍
thanks
I don't like this update :))
Well, the verdict is still out on this one as it’s not released yet. Hopefully, you’ll be able to find some common ground with this upcoming update versus older versions of Laravel. Time will tell, thanks for the comment 😀
This update was inevitable, since, previously almost 70% of the files and code would not have been needed to develop most of the apps online, however, they were there by default and making the app slower to respond in competition to other frameworks.
Now, after 11 we hope we will be importing and using what is only needed.
This is true depending on what you’re building. So you either have to refer to the documentation a little bit more or have knowledge of what was there before and reach for what you need. For example, replacing sqlite db with MySQL etc… in your .env file. Great comment.
🤮 hiding things doesn't make it better, it makes it 1000x worse.