"Laravel 10 is boring". *GOOD* . If I wanted to spend endless nights debugging ever-changing code, spend endless hours to stay up-to-date with the latest update that changes release version by "0.00.01" yet makes half code broken, then I'd work as a Javascript developer. No, like many, I make a living by delivering reliable, polished, consistent software. Laravel is very good but it always grated me the heavy "magic functionality" usage and the too frequent updates. Now we finally get something that won't break my schedule.
Completely agree. I still have a LOB app running on Laravel 5.3. When I look at the upgrade guide and the amount of breaking changes to move it up, I wonder in awe who is doing this in a production environment. Laravel is fantastic, but I think most users are the kind churning out greenfield apps and projects and then moving on to the next exciting thing. When it comes to supporting Laravel apps longer term in a real world production business environment, where development is just one of the hats I have to wear, stability and business continuity is the name of the game.
The fun never ends when there's upgrades... laravel/framework replaces illuminate/support and thus cannot coexist with it. - illuminate/support[v6.0.0, ..., v6.19.1] require php ^7.2 -> your php version (8.2.0) does not satisfy that requirement. - illuminate/support[v7.0.0, ..., v7.28.4] require php ^7.2.5 -> your php version (8.2.0) does not satisfy that requirement. - illuminate/support[v8.0.0, ..., v8.11.2] require php ^7.3 -> your php version (8.2.0) does not satisfy that requirement. and so on and so on...will get it all resolved eventually but as always it's more painful than anticipated.. 🤦♂
I have a problem. I want, should, update laravel to the latest LTS (9) version. The project is on 5.5. But the project is not small. Divided into modules. Has anyone done a similar update? Updating by version doesn't seem like a solution. You have to look for all the problems every time. And not all of them will be found. It seems that the best thing would be to take a new 9 version and transfer all the code. There will just be a lot of mistakes. 100% Until they are caught, there will be a lot of "trouble". Any suggestions?
It's not something that could be answered in a short RUclips comment. I'm thinking to maybe create a course on such scenario but still not sure, as such upgrade is usually weeks of work, not even days or hours. And yes for such old version I would probably recreate from scratch and copy parts
Laravel 10 requires php8.1 at least. Unfortunately, I have php8.0 since my servers are stateless EC2 built over Amazon Linux 2 which ships with 8.0. So I think I will be stuck with Laravel9 for a while
Your videos are always so great! They make me want to get back into coding. But I can't keep up any more. I spend hours debugging my apps and it takes me too long. Great video as always.
It's a long process. I would use Laravel Shift for this and upgrade version by version. Alternatively, create a new Laravel 10 project and then copy-paste separate parts from the old application. Also writing automated tests is a must for this. It would be actually a good course if your project is small and you're happy to share the code in public so I could help :)
![Tee Grizzley - Blow for Blow (feat. J. Cole) [Official Video]](http://i.ytimg.com/vi/wNLN5xsx5dc/mqdefault.jpg)
woah, even the video is exactly 10 minutes long
"Laravel 10 is boring". *GOOD* . If I wanted to spend endless nights debugging ever-changing code, spend endless hours to stay up-to-date with the latest update that changes release version by "0.00.01" yet makes half code broken, then I'd work as a Javascript developer. No, like many, I make a living by delivering reliable, polished, consistent software. Laravel is very good but it always grated me the heavy "magic functionality" usage and the too frequent updates. Now we finally get something that won't break my schedule.
Completely agree. I still have a LOB app running on Laravel 5.3. When I look at the upgrade guide and the amount of breaking changes to move it up, I wonder in awe who is doing this in a production environment. Laravel is fantastic, but I think most users are the kind churning out greenfield apps and projects and then moving on to the next exciting thing. When it comes to supporting Laravel apps longer term in a real world production business environment, where development is just one of the hats I have to wear, stability and business continuity is the name of the game.
Thank you for your videos!
The fun never ends when there's upgrades...
laravel/framework replaces illuminate/support and thus cannot coexist with it.
- illuminate/support[v6.0.0, ..., v6.19.1] require php ^7.2 -> your php version (8.2.0) does not satisfy that requirement.
- illuminate/support[v7.0.0, ..., v7.28.4] require php ^7.2.5 -> your php version (8.2.0) does not satisfy that requirement.
- illuminate/support[v8.0.0, ..., v8.11.2] require php ^7.3 -> your php version (8.2.0) does not satisfy that requirement.
and so on and so on...will get it all resolved eventually but as always it's more painful than anticipated..
🤦♂
Great review 🎉 thanks 🙏
rector can upgrade laravel for free. Shift is just a paid automated version of rector.
awesome, thank you
An actually nasty impact change is breaking feature is the change on DB::raw() when using multi index on DB with text fields... :(
Nice!
worth watching
If anyone has installed Laravel 10 with breeze dark mode, kindly inform if the UI is only dark mode or you can toggle
Idk man but you can do a manual toggle with some lines of js
the default dark mode is base on window system preference, you can change to class and make toggle for it.
Pretty sure Taylor used TailwindCSS. Have a look at TailwindCSS dark/light mode.
I have a problem. I want, should, update laravel to the latest LTS (9) version. The project is on 5.5. But the project is not small. Divided into modules.
Has anyone done a similar update?
Updating by version doesn't seem like a solution. You have to look for all the problems every time. And not all of them will be found.
It seems that the best thing would be to take a new 9 version and transfer all the code. There will just be a lot of mistakes. 100% Until they are caught, there will be a lot of "trouble".
Any suggestions?
It's not something that could be answered in a short RUclips comment. I'm thinking to maybe create a course on such scenario but still not sure, as such upgrade is usually weeks of work, not even days or hours. And yes for such old version I would probably recreate from scratch and copy parts
Laravel shift might help
Waiting for livewire 3
Please video about process
I don't personally use this. Marcel has written a good article about it: beyondco.de/blog/laravel-10-new-process-facade/
I cant link find php funny video
In the description of the video, the link about PHP 8.2
Better boring than funny but killing great packages because they became impossible to update in a easy way.
I just realize the minutes of the video is 10 like laravel 10 too
Laravel 10 requires php8.1 at least. Unfortunately, I have php8.0 since my servers are stateless EC2 built over Amazon Linux 2 which ships with 8.0. So I think I will be stuck with Laravel9 for a while
move to vapor
They've recently added php 8.1 to amazon linux 2 . Used to pull it from remi repo but now it's supported officialy.
I added the 999th like :) Gj Pavilas. Always a pleasure to watch.
is the video 10 minutes long on purpose? 😜
At first it wasn't but then I felt it's close enough, so edited it to be exactly 10 minutes :)
Thanks for your quick informative video.
+ 10 months ago
Do you use laravel shift for production environment?
Yes
Super overview
Hello, what do you think is the best framework for web developers? In general, what framework do you think is better than Laravel?
It is 10 and not 9.something because of the breaking changes.
For me it was removing annotations and replacing them with return types and type hinting the arguments, they were really annoying
do we will.see laravel with swoole to become concurrency
Thanks for your video
So why do I need Laravel Shift when upgrading from 9 to 10 is just upgrading the packages?
Convenience. And as I showed, it doesn't just perform the upgrade, does more work. But in case of Laravel 9 to 10, I agree it's not much.
Your videos are always so great! They make me want to get back into coding. But I can't keep up any more. I spend hours debugging my apps and it takes me too long. Great video as always.
that my friend is the essence of programming, you can't be a problem solver without problems.
thank you for updating us
Very decisive video. I’m interest in Laravel upgrade from 5.3 to 9
It's a long process.
I would use Laravel Shift for this and upgrade version by version.
Alternatively, create a new Laravel 10 project and then copy-paste separate parts from the old application.
Also writing automated tests is a must for this.
It would be actually a good course if your project is small and you're happy to share the code in public so I could help :)
Second comment
Thank you ☺
Stability
Any idea why Precognition is not in the docs?
I've done a video about it, and was waiting for it, but it seems the feature itself vecame kinda abandoned, not sure why