There's some seriously missing context to this post. It sounds like they are responding to some expectations posted elsewhere, but they don't link to what they're responding to. Or perhaps it's an update to something announced earlier, but they don't link to the past announcement. It's not clear what PHPng's relationship, if any, is to 5.5 or 5.6 in this post.
Anyone have any pointers to the conversation they are participating in with this post?
(mavci's link is an O'Reilly summary of the state of the PHP ecosystem and I didn't see any mention of PHPng.)
Yes, this is exactly what I was looking for. Thanks, rjknight. Someone visiting php.net without knowing the context would be seriously confused by this post (as I was).
There was a link a couple of days ago where I learned about phpng for the first time - it was some argument between php developers where core devs argued a change that made php5 nicer (standardised 64/32 field lengths / formats) made the phpng work harder. (undone some structure size optimisations) Maybe people discovered phpng that way and started asking questions about it? I can't find the actual link unfortunately.
If you Google "PHPng", you'll find a number of articles from the past few days about how the project is going to bring fancy stuff like a JIT compiler to the next version of PHP. Presumably this is to ensure expectations are set correctly and people don't think things are around the corner that actually aren't even in the country yet.
Anyone have any pointers to the conversation they are participating in with this post?
(mavci's link is an O'Reilly summary of the state of the PHP ecosystem and I didn't see any mention of PHPng.)
UPDATE: Perhaps this link is what started the confusion the php.net post appears to be trying to address: http://grokbase.com/p/php/php-internals/1455aesx7r/phpng-%04...