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

I worked with Laravel and trust me, it's a pain in the ass when you have a medium/big project. The "documentation" (more a how-to) is full of bad practices, the facade pattern makes it hard to refactor or change the underline logic, you can break the contract easily (it's just php annotations, not real type-hints), the ORM is a pain to test and has too much magic, you use strings to set the validation makes it hard to understand when it's not trivial, the request->input() takes query/body so you end up mixing everything and some clients use the API in various way, there is helpers to get the config/service anywhere (even in static methods) which makes it painful to test and refactor, etc. I strongly recommend to use Symfony instead, the documentation is great, the profiler is built-in, the cache is better (faster), it's type-hinted and strict, there is interfaces, it scales well because it's flexible and well thought.


> I worked with Laravel and trust me, it's a pain in the ass when you have a medium/big project

Every language is...




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

Search: