Today I'm going to give you three reasons why Laravel is a dying framework. For anyone in a hurry:
REASON 1: Worst in class benchmarks
REASON 2: Zero stability
REASON 3: Zero innovation
Shall I type about each of these things in a little more detail? Okay. Let's go. Reason 1: Worst in class benchmarks There's no denying that Laravel has ghastly benchmarks. It's slow. It's bloated. It's over-engineered. In the past, Taylor Otwell responded to this by saying that the reason why these kinds of claim are unfair is because people were using "fully loaded" Laravel applications for the various benchmark tests where Laravel gets consistently trounced. Given the fact that a fully loaded Trongate is now proven to be multiple times faster than Laravel, I don't think Otwell's excuse cuts in. I think benchmarks matter. The excuses aren't working. This is reason one. Reason 2: Zero stability Laravel is the most frequently rewritten of all the major frameworks. Until very recently they were committed to breaking their own framework every six months. Now, they're committed to breaking it every twelve months. This is not acceptable. Clients deserve better. Moreover, the "Laravel deception" - where developers mislead clients into paying for version upgrades under the false pretence of "security patches" is hereby called out. I think it's a scam and I'm looking forward to educating business owners about the Laravel Deception. What they have done is completely unethical, in my opinion. Regardless of the ethics, it seems clear to me that everybody is sick of rewrite culture. Clients don't want it. Developers don't want it. This is reason 2. Reason 3: Zero innovation Laravel does not have a single unique killer feature. Not one. Yes, it has lots and lots of bells and whistles. Some of them are nice. Some of them are positively good. However, that's not going to cut it. The fact is, there's not a single Laravel feature you can show me that's not already available from elsewhere. Laravel desperately needs a unique killer feature. Impersonating other technologies doesn't count. I think Laravel's failure to innovate is now becoming a huge problem that developers are finding difficult to ignore. All of these are things that I could have told you three years ago. What's new, however, is that - developers are starting to say 'no' to Laravel. That's real. That's new. That's a major development. So there you have it... Laravel is a dying framework. You heard it here first.
