Hi! > Maybe that would be a way to move forward with some of the log jams here?
I'm not sure where's the log jam here? An RFC proposing largely pointless deprecation not being met with overall enthusiasm is not a "logjam". It's a logjam only if somehow we were to imagine more BC breaks, more deprecations and more removal of functionality is somehow vitally necessary for PHP - which decades of thriving without all that amply prove to be false. I don't see what's wrong with just "do not break BC unless you absolutely can't avoid it" and why we need some grand World Council to arrive to this simple guideline that has been understood as obvious for years and has been also accepted by many other software projects? How comes now we have to spend so much time at affirming the obvious? -- Stas Malyshev smalys...@gmail.com -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
