3 ms·
You can use Laravel just for the basic wiring, integrated tooling, SQL query builder, auth, sessions, and HTTP routing. It really gets out of the way if you nee
by dgb23 5y ago
You can use Laravel just for the basic wiring, integrated tooling, SQL query builder, auth, sessions, and HTTP routing. It really gets out of the way if you need to avoid features you don't like. All of the stuff I listed above are a PITA in plain PHP.
- ThatMedicIsASpy 5y agoSymfony components would be the better choice? Did they change Laravel to only include what you want like Symfony?
- unfocussed_mike 5y agoYep -- Laravel has always been the work of grownups in this regard. It's a really very good platform for headless PHP. The job queuing stuff is so neat it actually makes me write queueable jobs. Combined with Lighthouse, Spatie's Stripe Webhooks library, Spatie's MediaLibrary, I've actually had fun with Laravel. I see no reason for hate now.
- cmg 5y agoI went kind of in another direction a few years ago - CodeIgniter's routing/sessions/etc base was plenty for most of my projects, but I wanted a real ORM. So I integrated Eloquent from Laravel and ignored the built-in CI database layer. A bunch of these sites are still running smoothly on modern PHP.