3 ms·

I worry that PHP's problem is that all these various frameworks are fragmenting developers, while Ruby on Rails is like a single beacon for Ruby devs. I've jus

I worry that PHP's problem is that all these various frameworks are fragmenting developers, while Ruby on Rails is like a single beacon for Ruby devs. I've just spent ten minutes going through the docs and I can't see anything that improves on what Yii has exactly the same functions for at least the last five months. That's not a criticism BTW, but I can't see any reason why FuelPHP would suddenly be a framework leader. Compare the docs contents: Fuel: http://fuelphp.com/docs/general/tasks.html http://fuelphp.com/docs/general/tasks.html Yii: http://www.yiiframework.com/doc/guide/1.1/en/basics.mvc http://www.yiiframework.com/doc/guide/1.1/en/basics.mvc

orthecreedence 15y ago
I agree. From reading the docs, and also having my head in several frameworks (including one I've developed) for over five years, Fuel really doesn't seem to bring a whole lot more to the table than is already there. While it may turn out to be a grand success (and I truly hope it is), I think PHP is, as you mentioned, much too fragmented to have an end-all-be-all framework of choice. Another successful framework will not unite PHP as much as add more fragmentation. This isn't necessarily bad (having more choices is fine), but a "one framework to rule them all" attitude seems a bit far-fetched (not that Fuel has this attitude, more the author).