32
Laravel keeps getting bigger and I'm not sure that's good (lemmy.world)
submitted 1 month ago by to c/programming@programming.dev
19 comments fedilink hide all child comments
 

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.

you are viewing a single comment's thread
view the rest of the comments
[–] 3 points 1 month ago (1 child)

if I was going to expand my horizons

Python is well liked and beloved, but it never captivated me or felt intuitive.

Writing magic init logic feels like a hacky workaround, like putting frameworks and concepts around what is, at its core, a scripting language. If you're committed to it, maybe you'll get past that barrier and find it's good, I don't know, I never got there. From outside, and with experience in other languages/ecosystems, it just never felt correct to me.

Have you considered alternatives? For example, C#/dotnet?

Just my experience/opinion. As I said, it seems well beliked by others. I can't speak for their views or experiences.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •