Originally from: http://www.sitepoint.com/best-php-frameworks-2014/
Update:if you ' d like to take part in the next High-yield survey from SitePoint, please vote for your favorite idehere. The aim of the survey is to gauge the PHP community, and to find the most popular IDE in use today, by gender, location, s Kill level, and more.
The end of the year is upon us. Lots have changed in the PHP World in the past 365 days, and the PHP framework scene are more densely populated than ever. Everyone and their dog seems to any of the idea of what a good framework should look like, but the the end, do we even know WH Ich frameworks actually end up being used in production projects? How many go beyond the stage for thousands of people just doing a demo app in them?
In a small survey we ' ve held open for the past week or so (which have also been mentioned in PHP Weekly), we asked these Qu Estions to decide which frameworks deserve we attention in. The prerequisite for participation is merely have experience in more than one framework, seeing as it's pointless to as K someone what their favorite bar is if they ' ve only drunk in one place.
Unfortunately, a big percentage of the answers had to being discarded due to people either refusing the notion that WordPress and similar suites aren ' t frameworks, or simply due to a blatant disregard of instructions–many responses were written By people who is only ever worked in one framework. While their enthusiasm for this framework of choice are noteworthy and admirable, the final result which may end up being s Kewed by such approaches could hardly be called objective.
Results Summary
After discarding the invalid responses, and manually verifying every participant, we were left with the following data:
According to the results, the most promising frameworks for seem to be:
Yii and CodeIgniter seem to is sharing 4th place.
After weeding out of the obvious spam, the Laravel results had to being filtered the most, by far. Over half the people who voted for Laravel had zero proof of proficiency, or experience only with Laravel, and had to be D Iscarded–despite this, it still prevailed.
When looking in the answers, on average, the Laravel community seems to mostly favor the ease of entry–virtually no Lear Ning Curve. Whether that's good or bad was a discussion for another time, seeing as we ended on this "PHP was bad" mess mostly due to A horde of newbies considering it an easy-to-enter market, but the excellent documentation, large scale community support and speed of development definitely work in its favor. Another frequently mentioned advantage seems to being an active and impressively alive IRC channel where help is given Instan tly.
An interesting misconception seems to be, Laravel is responsible for Composer. Many voters, both discarded and valid ones, mention Composer as the main advantage of Laravel, alongside eloquent ORM and The Blade template engine, which is downright odd seeing as Composer are a package manager completely oblivious to the Fram Ework it ' s being used with, if any. For more information, I urge the participants in question to read some of our Composer articles, like this one. Despite all this, has only tried Laravel in demo projects, the results of this survey has piqued my interest enough to Build my next production project in it, powered by HHVM.
Phalcon ' s main advantage was performance over other frameworks and the the fact that the framework is such a rounded up packag E (ORM, template engine, PHQL and More–all in One–little to no need for third party libs, meaning everything stays in- Memory, c-based and super fast). Some of the respondents noted the fact that it's installed as an extension as an advantage, because the process of the install ation weeds out of the hobbyists from the serious developers, a notion I personally tend to agree with. When mentioning cons, Phalcon ' s biggest one is also its biggest advantage–being written in C, it's nigh impossible to C Heck under the hood.
Symfony2 is touted as the most modular and extensible of the bunch, and the most feature complete, mainly due to Containin G Doctrine2. Its voters, however, does seem able to admit that it's quite bloated and slow at times due to this feature-richness.
Interestingly, ZF1 answers said they ' re stuck on said framework because of the work Situation–their team or CTO refu Ses to switch to something more modern.
RPM: PHP Development Framework Popularity ranking: Laravel top