3 ms·
> Why should I consider Laravel If you work on all those projects alone, and you're happy doing this, you probably wouldn't. You aren't the target market for a
by castis 5y ago
> Why should I consider Laravel
If you work on all those projects alone, and you're happy doing this, you probably wouldn't. You aren't the target market for a framework like this.
Laravel (and any good framework, really) is for people who want a consistent dev experience _with good documentation_.
- XCSme 5y agoYes, I do work alone on those projects, but I do use frameworks on the frontend-side as I find them to help in the long term, not hinder the projects as PHP frameworks do (a lot of boilerplate). It makes sense that if Laravel is strongly-opinionated to result in a consistent dev experience, but is a consistently bloated dev experience better than an inconsistent lean one?
- colecut 5y agoBloat can be mostly ignored, inconsistencies can not.
- unfocussed_mike 5y ago> You aren't the target market for a framework like this. I don't know about this. But then I am of an age where I consider myself to be a team of programmers separated by time. There are the younger, less easily tired versions of myself who thought this was a great idea for a career and lived on takeaway curries, there's me, and there are the four or five older versions of myself who will hate me for trying to be clever and not trying to be consistent. Laravel helps me take on projects that allow me to hand off pieces of work among my team ;-)