Programming

28424 readers

469 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Follow the programming.dev instance rules
Keep content related to programming in some way
If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev

founded 3 years ago

MODERATORS

snowe@programming.dev

Ategon@programming.dev

UlrikHD@programming.dev

bugsmith@programming.dev

Spyro@programming.dev

Laravel keeps getting bigger and I'm not sure that's good (lemmy.world)

submitted 1 week ago by indidev@lemmy.world to c/programming@programming.dev

20 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

[–] hoshikarakitaridia@lemmy.world 6 points 1 week ago* (last edited 1 week ago) (2 children)

yeah that's exactly where I am at.

I wrote smaller webservers in nodejs, flask, Django, Laravel, PHP/Xampp, and even C.

Xampp was hard, and modifying PHP files for other frameworks was difficult because it remains a very counter intuitive language for me, but in comparison Laravel was awful. It made absolutely no sense to me and that was about 5 years ago.

I'd literally prefer writing a webserver in rust before I wanna take another shot at Laravel.

[–] ThunderComplex@lemmy.today 7 points 1 week ago

Having only recently written a webserver in Rust, it's 100% the way to go. With Rust you don't get the batteries included thing and you write the glue yourself, but I'd rather do that than use something like Laravel for a small project. They're not even batteries included anymore, they're waaay beyond that.

[–] nicgentile@lemmy.world 4 points 1 week ago

When I was doing this project, and I was doing a presentation for the client, the client looked at me like WTF is this mess. And it was. I scratched it, restarted, kept it tighter, it was more tedious, but finally we are in beta testing. I did not appreciate this experience, and afterwards, I looked at everything and decided I was done with PHP.