Started with Laravel 4. Back then it was a lightweight framework — routes, Eloquent, Blade, done. Now the box ships with queues, broadcasting, events, policies, gates, notifications, API resources, Sanctum, Pennant, Folio, Volt, Prompts, Reverb, Pulse… The list grows every year.
For someone picking it up today, this isn’t a framework anymore — it’s an entire ecosystem where figuring out where to start is a project in itself. The docs are great, genuinely. But there’s so much of them now that just reading through everything takes a week.
On the flip side, when you need to ship a real product in a month — everything’s right there. No agonizing over which of 15 queue packages to use or hunting for a decent WebSocket server. Install Reverb, move on.
Feels like Laravel is heading toward becoming Rails for PHP — a platform that covers absolutely everything. The question is whether they can keep the onboarding simple. So far they’re pulling it off, but every release raises the bar just a little.
Python is a poor choice IMO. It’s just too slow, even for web servers. Everyone says “oh it’s IO bound or database bound; Python doesn’t matter”) but in my experience it does.
Better choices:
I just dipped toes into Rust for personal project and I definetly wouldn’t pick it up for web dev unless you have very very strict latency requirements or massive throughput. Too much hassle. C# is also a good option now that its cross platform.