intertwingly

Round-up of ES4 discussions for the past few days:

• Like it or not, with JavaScript, JScript, ActionScript and others in play, ECMAScript is fragmenting.  There is an opportunity for the players involved to work together to converge.  That presumes that the motivation is there for them to do so.
• ES4 is intended to be a superset of ES3.  Your one liners in onClick attributes will continue to work.  The magic that is prototype will continue to work.  In addition, there will be classes, packages, and optional type annotation, to name but three of the many new features.  To some that may be bloat, but every indication is that compatibility will be maintained and performance overall will not suffer; furthermore there is no requirement that you have to use every feature of the language in every script.
• Brendan did not earn his civility badge last month.  Personally, I think badges are overrated.
• As always, no new specifics emerged from the secretive northwest.  Even if ES4 were renamed ES5 to make room for a bridge release, every issue that needs to be addressed in ES4 would also need to be addressed in ES5.  Specifics would be helpful here.  Again, the question goes back to whether the people involved are motivated to be helpful here or not.

Did I miss anything?

Update: Brendan now has published his own round-up.

There is a bug in Ruby 1.8.6 that affects documents with a default namespace (even a vestigial one, like those sported by WordPress weblogs) which prevents non-namespace qualified attribute names from working in XPath expressions.  The following monkey-patch fixes this:

...