On Tue, 4 Oct 2005, Bart van Bragt wrote: > Starting with a clean slate would cool for you (it would enable you to do new > and cool things) but it would either force us to switch to a more stable > language or keep two completely different codebases. I know what I would > choose.
But who says your code should run on the new version? You don't *have* to upgrade per se. It merely allows newly developed projects to run on a cleaner version of PHP, which would undoubtfully also be faster (because we wouldn't have any BC ballast). > There are some whacky things in PHP4 and PHP5 that need to be fixed and to fix > that BC sometimes breaks. No problem with that. The problem is that you're > breaking BC again while almost no-one has switched to PHP5 yet because of the > BC breaks between 4.x and 5.0. Are you sure it's because it breaks BC? We don't know why people don't migrate. And for us, we didn't migrate because *we* want to start with a new clean code base too, and not something hackish that just makes it work with PHP 5. > Breaking BC again is certainly not going to help the adoption of PHP5. It's not going to help people to "migrate their code", that's for sure. But as I said before, you don't *have* to upgrade. > Please just accept that things can't move at the speed that you'd > like. It takes ages before people upgrade, that's just the way it is. > Breaking BC won't force people to upgrade, it will keep them from > upgrading. Yes, but it will also result in PHP being less and less competitive because we have to maintain all the old (broken) behavior (and make sure we never change anyting there). Derick -- Derick Rethans http://derickrethans.nl | http://ez.no | http://xdebug.org -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
