Rasmus Lerdorf wrote:
Hans Zaunere wrote:
That presents somewhat of a chicken-and-egg problem. Production sites won't be compelled to make a move until PHP
recommends it in some way, or if there is a killer feature
that pulls people in, regardless of the perceived stability.
Right, and they shouldn't. If there is no compelling reason to switch, why in the world should they? And why should we try to push them away from a stable platform?
Absolutely. All things considered, the gap between PHP5 and Apache2 is understandable. Killer features don't draw people, solutions to killer problems do. When using Apache-2.x offers a solution to a killer problem that Apache-1.3.x can't solve, that gap will close on its own. I can't imagine why anyone would want to tamper with this process, it has worked so well for so long.
It is not quite that simple.
Firstly, it is important to realize that there are people who have killer problems or want killer features from Apache2, it is just that none of those people are PHP devs. This is why the topic keeps getting rehashed. But for better or worse, the issue won't be addressed until the PHP devs (or someone else who is sufficiently knowledegable) feels the need to address it because it affects the systems use/manage/care about in their day to day lives...that is just how the system works.
Secondly, just because I don't have a killer problem *yet* doesn't mean I should indefinitely delay upgrading. There is some value in staying current with the product that is being actively devloped. It isn't always the best way to go about things, but sometimes it can be less painful to do your upgrades incrementally rather than have one huge revolutionary change. Some the Apache2 features that I am most interested in (LDAP and WebDAV related) won't be available till 2.2. however if I waited till 2.2 to do the upgrade from 1.3, and setup the new LDAP and WebDAV stuff at the same time, I would have a lot more balls in the air than if I had just stayed "current enough".
I am not saying that the PHP devs should be forced to fix problems that they don't have. I am just saying that it isn't all as simple as you are making it out to be.
Marc
-- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
