Mac Newbold wrote:
I would have been much happier if PHP5 was more backward compatible,
and added new functionality without breaking old functionality, and
simply deprecating it. Then in PHP6, they could remove the old stuff
after people had time to get used to the new stuff. If you want people
to upgrade, you need to make it as painless as possible, and as
valuable as possible, or people will hold out until the cost is lower,
the value is higher, or the cost of not upgrading gets too high to bear.
Anyway, it's a sad commentary that discussions like these are still
happening after 3 years. It is a real problem, and a big one, and I
hope the PHP team, as well as other open source projects, learn a
whole lot from the mistakes that were made this time, and don't repeat
them.
Well put - it tells me it's a kiss of death if the core development team
isn't careful enough to deprecate properly. The same thing has happened
to FLTK (c++) where the new version 2.0 is not backwards compatible
enough to have people encouraged to upgrade. It's another confirmation
to me that using another progressive codebase such as Rails is a better
approach (not to mention productivity from a standardized framework).
Wade is right in that Apple managed to move everyone over to OSX and now
who even thinks about the old OS? And MS has in the past managed to do
the same thing (though they broke enough with Vista to create a real
upgrade backlash).
_______________________________________________
UPHPU mailing list
[email protected]
http://uphpu.org/mailman/listinfo/uphpu
IRC: #uphpu on irc.freenode.net
