Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Since this has generated quite some interest, the reasons I dislike Laravel are:

- so. many. godobjects.

- I dislike ORMs. I could not put my finger on it, while using PHP frameworks, because they were omni-present; but after using Python, Go, and C#, I found it to be easier for me to just avoid the overhead of an ORM.

- Terrible structure. Sorting classes by type is something I have experienced to be generally less helpful than sorting by "topic" (not a native speaker, so this might not be the correct word for it. I recently heard it compared to collecting cars, then disassembling them and sorting by tires, steering wheels, seats, and so on)

- Too much magic™. I understand that many like this about it, but I found it harder to understand what exactly the program is doing.

It's not a lot, but after literally years of PHP and having these paper cuts almost weekly, I was at one point fed up. I first switched to CodeIgniter, which I found more pleasant, but still not even comparable to the comfort that cherry-picking components gets you (yes, you can by using composer, but most people I have spoken to discouraged that in favour of Laravel's built-in fun).



I agree Laravel is a bit too much magic, but I’ve found Eloquent to be a top notch ORM. It hasn’t really failed me in any way, so I’d be interested to hear what you specifically disliked about it.


While I enjoyed my (small) foray into the world of Laravel, I'm happy to see something other than unabashed praise for Laravel here on HN.

A technical decision should be done by weighting it's pros and cons, not just by looking at the pros.

Agree on the 'Sorting classes by types', it's something I've always found surprising too, and love the car-collection metaphor.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: