Larry Garfield wrote: > It's great to hear you say that, given that the messaging coming out of > WP at the time was rather hostile. :-)
As I noted, the dynamics have changed significantly. I'd say that core committer team as a whole is now much less conservative than before, although they're still just as dedicated to internal backwards compatibility. As an example, it's looking like PDO is almost a certainty for 3.6. It will mean some backwards compatibility issues though, so a while ago, this wouldn't have even been considered. (Note: I'm not a core committer, mainly due to never having the time to commit to it, but I am heavily involved in WP development. I'm also single-handedly responsible for ~10% of the codebase via SimplePie.) > I don't know much if anything about WP internals, but in my experience > with Drupal 8 LSB is about the only 5.3 feature that hasn't mattered to > us. Namespaces/PSR-0 and closures have been very helpful. LSB not so > much, but then I'm pleased to say we have very little static method use > in the first place. Namespaces don't matter to WordPress really, since it'd only be new code using them anyway. Changing existing class names would be a huge internal backwards compatibility break which I doubt will ever happen. Closures, as I mentioned, don't work well with our action/filter system. Basically, in order to be able to unregister a callback, you need to pass in the exact callback that you registered it with; with closures, this isn't possible unless they're assigned to a variable, which defeats the purpose. > Maybe next year it will be time for a GoPHP5.5 project. :-) Hopefully by > then WP will have become less conservative enough to join the effort. Here's hoping. :) -- Ryan McCue <http://ryanmccue.info/> -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
