DEV Community

Discussion on: Decision Time: PHP Framework Dilemma

Collapse
 
bcalik profile image
Burak Çalık • Edited

Hello, I'm the CTO of a small software development company with 35 people. We use PHP for most of our solutions. Framework of our choice is Laravel, we use it since Laravel version 3, at very early stages. We also tried Symfony for a few large scale projects, but probably we will never use it again.

Unlike Symfony, Laravel gives you all the stuff that you will most likely need. Saves your hundreds of hours in a long run. It has many built-in solutions like Queue, Filesystem etc. Eloquent has awesome built in solutions for eager-loading, polymorphic relations etc. The best part is that every developer don't need to learn every single project's structure and features, because its all same for all Laravel projects. When a new developer opens any project, he only needs to learn the business logic and the architecture, then he is ready. He knows how the things are working and he can immediately start developing.

Laravel is very well documented, and also very easy to understand.

Btw, stop about thinking developing your own framework or using spaghetti PHP. Every junior falls the same mistake. After using a real framework, you will never look back, and will laugh when someone says "Hey I developed my own framework".

Collapse
 
syntaxseed profile image
SyntaxSeed (Sherri W)

Not planning for a second to roll my own framework again. No way.