Symfony, Yii, Zend, Laravel
- Thread starter jipol
- Start date
reynerhl
New member
Right now, from my point of view, in the PHP enviroment Laravel is the most powerful framework. It has a great community, great documentation, takes the best of many other frameworks (such as Symfony, ORM/ActiveRecord).
Take a look at the google trends, perhaps is not the way for determining wich one is better but if many people are changing their search terms, there would be a good reason.
https://www.google.com/trends/explore?q=/m/0jwy148,/m/09cjcl,Yii,/m/0cdvjh
Take a look at the google trends, perhaps is not the way for determining wich one is better but if many people are changing their search terms, there would be a good reason.
https://www.google.com/trends/explore?q=/m/0jwy148,/m/09cjcl,Yii,/m/0cdvjh
reynerhl said:
Finally someone who use frameworks! Thank you for your opinion!
Well, I'm absolutely the Symfony guy! I don't think the Laravel can win comparison with Symfony if we're going to compare the community size and available documentations. I think the Symfony, being more mature, has bigger community. When it comes to the actual features of frameworks, it is much harder to compare. Symfony has great modularity, while Laravel not so much. Personally, I love Doctrine. In my opinion it's better than Eloquent (which is a bit simplified). The additional control via getters and setters in entities (and documents) adds another layer of flexibility. Powerful decoupled repositories. I heard the Laravel has worst performance in prod environment. But, of course, in the end it all comes to the personal preferences.
smalpierre
New member
I voted for "don't use / don't like" - but I DO use them ... I just don't like them. They're a tool, and I've filtered through a LOT of garbage to come up with what I use. I don't like them because they add overhead. Usually a LOT of overhead - and I don't use them for much.
The one I use and like most, is Phalcon. You've got to have a VPS because you're installing Apache modules, but most all my sites are on a VPS now anyway. My second in line is Laravel. It's by far the most popular, and has a larger community which is helpful. I've used Slim more, because I don't use tons of framework functionality, and I'm adverse to Composer.
Phalcon is an Apache module so it's compiled in C giving it the potential to be faster than any framework in PHP (provided it's coded reasonably well, and it is). I use a framework basically for routing, and a template engine. I can get both without one, but why? I don't use ORM, and I really don't like it. My models are classes that run sql. My front controller doesn't use "mvc" routing where the url is /controller/method/variable1/variable2 ... I define them all. So I don't need or want a heavy framework. I don't like my code interspersed with a million libraries I'll never use. I don't like to dig through frameworks code to get to directories where my controllers are, or where my views are. So Phalcon, it's all your code in PHP, you're calling C code through the Apache module instead of a a bunch of crap in the Composer directory structure.
Best for me: Phalcon, because devops isn't a problem, it's template engine is excellent, and it's all fast.
Best for most: Laravel, because all the tutorials / walk throughs love Composer, and Laravel is made for that environment. It's very full featured, and the most popular by far. Best documentation, and it's respectably fast considering it's features.
Best for some: Slim. Especially if you're building an API and all you need is a router. You can even drop Eloquent in there if you need an ORM. I used to use it with Twig - but since I do the "no Composer" method, it's install isn't any easier than Phalcon which is orders of magnitude faster.
The one I use and like most, is Phalcon. You've got to have a VPS because you're installing Apache modules, but most all my sites are on a VPS now anyway. My second in line is Laravel. It's by far the most popular, and has a larger community which is helpful. I've used Slim more, because I don't use tons of framework functionality, and I'm adverse to Composer.
Phalcon is an Apache module so it's compiled in C giving it the potential to be faster than any framework in PHP (provided it's coded reasonably well, and it is). I use a framework basically for routing, and a template engine. I can get both without one, but why? I don't use ORM, and I really don't like it. My models are classes that run sql. My front controller doesn't use "mvc" routing where the url is /controller/method/variable1/variable2 ... I define them all. So I don't need or want a heavy framework. I don't like my code interspersed with a million libraries I'll never use. I don't like to dig through frameworks code to get to directories where my controllers are, or where my views are. So Phalcon, it's all your code in PHP, you're calling C code through the Apache module instead of a a bunch of crap in the Composer directory structure.
Best for me: Phalcon, because devops isn't a problem, it's template engine is excellent, and it's all fast.
Best for most: Laravel, because all the tutorials / walk throughs love Composer, and Laravel is made for that environment. It's very full featured, and the most popular by far. Best documentation, and it's respectably fast considering it's features.
Best for some: Slim. Especially if you're building an API and all you need is a router. You can even drop Eloquent in there if you need an ORM. I used to use it with Twig - but since I do the "no Composer" method, it's install isn't any easier than Phalcon which is orders of magnitude faster.
ardon:
muraziii
New member
I chose Other because I used to study CodeIgniter in school. However, I don't really code backends so much so my opinions don't really matter lol. Anyway, if I really do going to code backend again, should I use Laravel? My friends suggested it to me and I see a lot of positives in here. It'd be appreciated if someone can tell me where to start. Thanks!