Yes, PHP will never have something unifying like Rails. But are there really too much frameworks out there? I don't think so. Competition is a good thing. It is about choice, striving for new ideas and combining them in ways no one thought before. I believe that Ruby in the long run has a serious drawback in only having Rails. Because there is only Rails people who don't like it will not start using Ruby because they don't have the choice to use another framework.
But I admit, there is a problem with too much frameworks. Its about specification. PHP has no specifications. The lack of the PHP community to define such specifications will bring a lot more of new frameworks for us in the future that are not compatible. In Java no one complains about competition between frameworks. They have specifications, and frameworks stick to those making it easier to switch between them because they have the same API. Yeah, I know PHP is not Java. It should not be in the language. But it should learn from their way of defining specifications. As long as this does not happen the rants about YAF™ (Yet Another Framework) will not lead us anywhere.
Enough ranted. In a forthcoming blog entry we will write why we develop Stubbles and did not stick to another framework. Stay tuned.
Wishlist pt 3 opposed: specifications instead annotations
In part three of his wishlist for PHP 6 Stephan wrote that he would like to see annotations built into PHP 6 directly. I disagree with him about that. Annotations can be done in userland, without any problems. He already gave some examples of projects tha
Weblog: Stubblog Tracked: Feb 25, 15:42
Why we develop Stubbles
In an earlier entry I promised that we will explain why we develop Stubbles. Well, there is a short version of it and a long version.
Short version: for us.
Read on for the long version.Long Version:
Release cycles and maintenance requirements
With all due respect, I don't think the response was triggered simply by the announcement of Stubbles and the Stubblog. It was the indeed quite curious coincidence of having three new frameworks being announced in the short timespan of a few hours.
Having said that, I definitely support your call for specifications. I've written before on the topic of the need of a JSR-like specification for PHP on my weblog. Of course, with me being a simple PHP developer, the idea's never been picked up, and I am not the person to pick it up either I think. But having a set of specifications would be so good for PHP and the PHP community...
One of the other problems is that it sometimes takes using three different PHP frameworks to rapidly prototype and develop an web application.
Please explain me, why you don't use eZ Components!
* They have a classloader around PHP's native autoload
* They have an event component (SessionSlot)
* They have an exception handler
* Their documentation is far better then yours
* They also use UnitTests
They don't have a XML Template engine, but you could easily combine your stuff with eZ Components.
> They have a classloader around PHP's native autoload
We do not want to use PHP's native autoload mechanism.
> They have an event component (SessionSlot)
Do you mean SignalSlot? This event component has no event queuing and bubbling, its mostly tight with the concrete class instance that wants to send a signal (if you don't want that you have to use another class), and most important they can not cancel events. To make the latter point work in their event component it would need a complete overhaul in my eyes.
> They have an exception handler
That's fine for them. Maybe we will have one too, maybe we will use one of another framework. That is up to decision when we need this.
> Their documentation is far better then yours
We just started, so don't expect full documentation yet. Additionally the question of how good a documentation is is just a point of view.
I had the privilege of getting a personal demonstration of Stubbles this week by Stephan, and I really like the direction the project is taking.
The whole Yet Another Framework discussion is quite interesting in that an effort to combine all the individual developements on separate frameworks would definitely be an asset for PHP. But why are renowned developers like Clay Loveless then not using the Zend Framework, which strives to set a standard for PHP frameworks? I can only guess, but I know I do not use it because I do not like it - it does not work the way I want it to. In that sense, the current diversity is an advantage because I will more likely be able to find a framework that fits my expectations and needs.
In the end, as Frank stated I think the whole discussion is really rather pointless as long as there are no specifications/standards... Until then, let them all build as many frameworks as they like. Through natural selection only the good ones will survive anyway. Will Stubbles be one of those? I cannot say, but I believe there definitely is a place for it.