I think one of the biggest change was how routing works. Before: Route::get('/', 'PostController@index'); Now: Route::get('/', [PostController::class, 'index']); You can enable the old way, but when this was introduced I was pretty confused.
Moving fast or not: Laravel has completely changed the course of my life and career. I can't imagine my life now without it. It seriously is the greatest thing for any PHP-dev since sliced bread.
Upgrading from Laravel 8 to 10 broke a BUNCH of stuff, because I was still using some DB:raw() queries, and that was no longer supported in 10. I had a hell of a weekend re-writing nearly every single one of my queries. Some were quick, but the more complex queries with multiple joins and inner select statements took a while to figure out.
Really?? I can't believe that to be honest. Nevertheless I was about to migrate to 10 these days, thanks for the heads up regardless if this is true or not
Wow I take my words back, indeed DB::raw() isn't supported as it was. I'm surprised that not many people flagged it as an issue, perhaps low number of devs use it that way?
I personally am making an effort to be more open to changing with Laravel because, in the end, it tends to lead me in a positive direction. Transitioning from Bootstrap to Tailwind, switching from Mix to Vite, and exploring Vue, among other things, have helped me stay updated on the latest industry practices. When it comes to communication, it's an interesting point to consider, but I'm not sure if there's a better approach. Excessive communication can potentially hinder progress and dampen the innovative work taking place. However, I appreciate the fact that he responds to community feedback, which is beneficial. Thank you for sharing the video.
I'm very new to Laravel (started a month ago) and this explains a lot. Searching online for solution for problems can be confusing because the framework has apparently changed quite a lot. And it doesn't make it easier I use the new Vue Composition API, which you rarely see being used in examples! But I'm getting there. It's a great stack!!
Also worth to mention that laravel changes the minimum required PHP version with each major version, so it’s good to have that in mind as well. Great video by the way, would be very interesting to see a video on upgrading from v5 to v10 😄
I've worked with many frameworks so far, but Laravel is a well thought out framework with great versioning. You can jump back to any package at any time
I've been using Laraval since version 5. It updated to version 6 before I had even finished my program. I am still using Laravel to this day, now it's at version 10. From version 5 to version 8, Laraval changed drastically in my experience. Not so much from version 8 to version 10.
@@LaravelDaily Yes as the Bumble Bity said, I had to spend a lot of time refactoring the code to get it to work with the new version when 6, and 7 came. But recently when I updated my Laravel 9 app to Laravel 10, all I did was change some package versions in the composer.json file. I don't remember the exact changes I did since it was long ago.
In the default project skeleton (laravel/laravel) alone, there have been 95 files changed between 5.5 and the current release. In the framework itself, around 2.2k files have changed between 5.5 and the current version. So, yes, Laravel has changed significantly since 5.5. While some code might work from back then, there will probably be some adaptations required due either changed method signatures, deprecated/removed methods, class-based factories, etc.
The factories have also changed, from factory(Model) format to Model::factory()->create(), around Laravel 8. Initially I installed the compatibility package to allow them to continue working, but after a while I spent a couple of hours going through hundreds of tests and updated all.
@@LaravelDaily No, this video is more about the packages/ecosystem that has been changed. I'm talking about things that no longer work, as an example one comment mentions Route::get('/', 'PostController@index') controllers
really simple project may take a day to move and some project needs some more days, but it's not critical if you have unit tests or somekind testing environment
Hi, there were changes in laravel auth and guards in 5.x you coulnd't get a lot information in controller, there are far more thing'S then you mentioned.
It's not about slow pace as in less "big things" have happened... the general API has changed quite enough for more intricate development. Say "it hasn't changed a lot" when you have to do manual upgrades.
To streamline the process, kindly specify the video you're referring to and incorporate it into the video by adding an "i" button. Your cooperation is appreciated. Thank you.
It's hard to adopt changes, but in reality we need to, our server Linux version need to update because of LTS and does the php version and Laravel affected.
I started learning laravel not very long ago at version 8. Then I picked up old projects written by other Devs in version 7. It wasn't a problem at all. When I picked up version 5, I was pretty confident till I came across the Form blade directive. I had worked with laravel for several years and didn't know this existed. So, yeah I can agree laravel doesn't move too fast. But some changes could be very polarising. Imagine how many forms exist in any project, to have to deal with that.
it massive changes compared with CI, I just foll since 4.x structure directory changed i don't follow again. just follow email news everything updated time by time 😅
At my company the application code base is around 15 to 20 years old. We are looking at building a new platform based around laravel but how are you meant to make a long term application like this when things change so much? There is no way we are going to constantly upgrade it like this.
You dont have to. Our client still happy with our project built in Laravel 6. We dont have to change major stuff, only bug fixes every few weeks. Only build with newest for new project. after that just stick with whatever version you use.
I thought to convince you with this video that Laravel is NOT changing fast, and most changes are optional. I guess I failed at this :) feel free to not use Laravel if you don't want to
Hi Laravel Daily, I'm a junior php developer in a company , they work with core php , in that case should I leave the company and move to any other opportunity who works with laravel ? I'm pretty confused about that .
Vite seems to have broken the Laravel Modules package? How would you use Laravel Modules with Vite bundler and have a modular app now? Since Laravel Modules uses webpack
@@LaravelDaily Yeah, I just watched your video about Laravel Module package the other day, thought about using it in my current project which is 10.x version, but read in Laravel Modules docs that they use webpack and then tried to search the internet for solution for Vite. Kinda doesn't exist yet.
I think PHP's and Laravel's biggest problem is the lack of desktop and mobile app support. While Javascript, C#, Flutter and probably some other languages/frameworks are offering an ability of creating everything with a single language/code base, we have to use at least one more language to be able to cover multiple use cases. I think PHP or Laravel team should focus on that area, otherwise sooner or later both will die.
Over here Wondering why this guy pushed for functions to define what hey return.... that's so unnecessary.... Let people return what they want to return
I think one of the biggest change was how routing works.
Before: Route::get('/', 'PostController@index');
Now: Route::get('/', [PostController::class, 'index']);
You can enable the old way, but when this was introduced I was pretty confused.
Yes, good point, many people were confused at that time, indeed. Should have mentioned it in the video.
I second this. I was like wtf is wrong with my routes now, I just started creating a new app, don't need this bs :D
Moving fast or not: Laravel has completely changed the course of my life and career. I can't imagine my life now without it. It seriously is the greatest thing for any PHP-dev since sliced bread.
It's garbage
@@frankyboy1806why?
Upgrading from Laravel 8 to 10 broke a BUNCH of stuff, because I was still using some DB:raw() queries, and that was no longer supported in 10. I had a hell of a weekend re-writing nearly every single one of my queries. Some were quick, but the more complex queries with multiple joins and inner select statements took a while to figure out.
Wait what? Laravel 10 doesn't support DB::raw()?
Really?? I can't believe that to be honest. Nevertheless I was about to migrate to 10 these days, thanks for the heads up regardless if this is true or not
Wow I take my words back, indeed DB::raw() isn't supported as it was. I'm surprised that not many people flagged it as an issue, perhaps low number of devs use it that way?
Ouch.. that could be really frustrating :(
I personally am making an effort to be more open to changing with Laravel because, in the end, it tends to lead me in a positive direction. Transitioning from Bootstrap to Tailwind, switching from Mix to Vite, and exploring Vue, among other things, have helped me stay updated on the latest industry practices.
When it comes to communication, it's an interesting point to consider, but I'm not sure if there's a better approach. Excessive communication can potentially hinder progress and dampen the innovative work taking place. However, I appreciate the fact that he responds to community feedback, which is beneficial.
Thank you for sharing the video.
I'm very new to Laravel (started a month ago) and this explains a lot. Searching online for solution for problems can be confusing because the framework has apparently changed quite a lot. And it doesn't make it easier I use the new Vue Composition API, which you rarely see being used in examples! But I'm getting there. It's a great stack!!
Vue is a different topic. Composition API is totally different from the old one, so you have to be careful reading which version is the tutori for.
Also worth to mention that laravel changes the minimum required PHP version with each major version, so it’s good to have that in mind as well.
Great video by the way, would be very interesting to see a video on upgrading from v5 to v10 😄
I've worked with many frameworks so far, but Laravel is a well thought out framework with great versioning. You can jump back to any package at any time
Thanks for the video
Spotted Cosmic Gate !!!!!!!!!!!!!!!! Oh man, all the best and a big Thank you for all your work.
Yup, big fan of cosmic gate :)
I've been using Laraval since version 5. It updated to version 6 before I had even finished my program. I am still using Laravel to this day, now it's at version 10. From version 5 to version 8, Laraval changed drastically in my experience. Not so much from version 8 to version 10.
What exactly you would point out as "drastical" changes that I missed?
@@LaravelDaily He means that he did some serious refactor to run app in newer versions of Laravel.
@@LaravelDaily Yes as the Bumble Bity said, I had to spend a lot of time refactoring the code to get it to work with the new version when 6, and 7 came. But recently when I updated my Laravel 9 app to Laravel 10, all I did was change some package versions in the composer.json file. I don't remember the exact changes I did since it was long ago.
In the default project skeleton (laravel/laravel) alone, there have been 95 files changed between 5.5 and the current release. In the framework itself, around 2.2k files have changed between 5.5 and the current version. So, yes, Laravel has changed significantly since 5.5. While some code might work from back then, there will probably be some adaptations required due either changed method signatures, deprecated/removed methods, class-based factories, etc.
The factories have also changed, from factory(Model) format to Model::factory()->create(), around Laravel 8. Initially I installed the compatibility package to allow them to continue working, but after a while I spent a couple of hours going through hundreds of tests and updated all.
Good point, yes, should have mentioned that one in the video, too.
Nice video, cheers!
Good, I have same in opinion with you. Nice video, thank you.
How about a video of the most breaking things from version 5 to 10?
Isn't it the same I just mentioned? Or what do you mean.
@@LaravelDaily No, this video is more about the packages/ecosystem that has been changed. I'm talking about things that no longer work, as an example one comment mentions Route::get('/', 'PostController@index') controllers
Most of the work in upgrading from 5.5/6 is to adapt methods to PHP 8.1+ syntax...isn't it?
Yes required PHP versions need to be upgraded on the server, and OPTIONALLY you may choose to use PHP 8 syntax if you want to.
really simple project may take a day to move and some project needs some more days, but it's not critical if you have unit tests or somekind testing environment
Nice thumbnail👍
Hi, there were changes in laravel auth and guards in 5.x you coulnd't get a lot information in controller, there are far more thing'S then you mentioned.
It's not about slow pace as in less "big things" have happened... the general API has changed quite enough for more intricate development.
Say "it hasn't changed a lot" when you have to do manual upgrades.
please help me, How to implement the inheritance? (Thanks for your videos I enjoyed them).
To streamline the process, kindly specify the video you're referring to and incorporate it into the video by adding an "i" button. Your cooperation is appreciated. Thank you.
It's hard to adopt changes, but in reality we need to, our server Linux version need to update because of LTS and does the php version and Laravel affected.
I started learning laravel not very long ago at version 8. Then I picked up old projects written by other Devs in version 7. It wasn't a problem at all.
When I picked up version 5, I was pretty confident till I came across the Form blade directive. I had worked with laravel for several years and didn't know this existed.
So, yeah I can agree laravel doesn't move too fast. But some changes could be very polarising. Imagine how many forms exist in any project, to have to deal with that.
it massive changes compared with CI, I just foll since 4.x structure directory changed i don't follow again. just follow email news everything updated time by time 😅
For me. moving away from bootstrap/Vue to Tailwind is the what actually changed.
At my company the application code base is around 15 to 20 years old. We are looking at building a new platform based around laravel but how are you meant to make a long term application like this when things change so much? There is no way we are going to constantly upgrade it like this.
You dont have to. Our client still happy with our project built in Laravel 6. We dont have to change major stuff, only bug fixes every few weeks. Only build with newest for new project. after that just stick with whatever version you use.
I thought to convince you with this video that Laravel is NOT changing fast, and most changes are optional. I guess I failed at this :) feel free to not use Laravel if you don't want to
@@LaravelDaily you convinced me it's not as bad as I initially thought
@Aizuddin Yusoff yes this is the conclusion I came to also
Hi Laravel Daily, I'm a junior php developer in a company , they work with core php , in that case should I leave the company and move to any other opportunity who works with laravel ? I'm pretty confused about that .
It's a personal preference, if you're happy with current job then why look for another?
I have also heard older devs say that nothing has really changed in years in Laravel 😅
Vite seems to have broken the Laravel Modules package? How would you use Laravel Modules with Vite bundler and have a modular app now? Since Laravel Modules uses webpack
Not sure, haven't tried modules package in a while, you could raise an issue on their repository.
@@LaravelDaily Yeah, I just watched your video about Laravel Module package the other day, thought about using it in my current project which is 10.x version, but read in Laravel Modules docs that they use webpack and then tried to search the internet for solution for Vite. Kinda doesn't exist yet.
Well alternative option is to change to use Webpack again.
Eloquent relationship changes that are not mentioned, and many more.
Relationship CHANGES? You mean additional new functions like one-of-many?
It's not changes, it's new features, it's not the same.
I guess something wrong with me, 5:40 I don't use any CSS framework in my project (online store), just pure CSS.
Nothing is wrong, use whatever you prefer
I'm a person who's not very good with change in general, I was hurt about webpack and laravel UI
I think PHP's and Laravel's biggest problem is the lack of desktop and mobile app support. While Javascript, C#, Flutter and probably some other languages/frameworks are offering an ability of creating everything with a single language/code base, we have to use at least one more language to be able to cover multiple use cases. I think PHP or Laravel team should focus on that area, otherwise sooner or later both will die.
Couldn't a js desktop app still use laravel backend api?
Over here Wondering why this guy pushed for functions to define what hey return.... that's so unnecessary....
Let people return what they want to return
It’s so hard to watch this video for people who still have Laravel 5.5 version and forcing PM to update it to 10 version🥲
Yes, it’s me😅
There there :)
That makes 2 of us 😅