| I‘d encourage you to seriously give Laravel a shot. I’d fundamentally disagree on it being harder to learn than the language itself. > You can always do better when you start with the domain you are solving and work from there rather than trying to adapt your domain to some generic solution. I’d even agree! In my view this as a reason to go pro-Laravel and similar opinionated frameworks.
They allow you to focus on what actually matters, which is your specific business logic. Define your data models and the rest follows automatically. Use API Platform to automatically generate a REST API from just your models. Need custom logic in there? Use middleware or define your own routes. You’re really not being hindered by the framework in any way I can think of. Laravel is truly a beast and IMO not comparable to older Java frameworks. You don’t have to use these features tho. You don’t have to use the ORM and you could even write your own routing if you really wanted to. To me, this is what makes a good framework: providing everything out of the box for 80/20 solutions and provide appropriate escape hatches if you ever need to do something entirely custom. Want a react frontend? Use Intertia and get started writing UI and interactivity instead of setting up data flows. Want automatic backends? Use Filament and get Schema-based forms and tables for free. But I have yet to encounter web app use-cases that go beyond of what Laravel could handle. Something like this in the Go world would make a great addition, provided there are alternatives and escape hatches present (idk if that’s the case). |