Why JS2 Does Not Matter:
Although Mozilla acts as if they inherited Netscape’s mid 90s status as keeper of the web platform, this is not the case. They say that it doesn’t matter is Microsoft adopts JS2 or not, they’ll just write an IE plugin. This may work to increase JS2 adoption, but it doesn’t actually solve any real problems. JS2 is a solution looking for a problem.
When building TileStack, my main problem with JS isn’t some language feature (native classes, typed variables, etc.) it’s the lack of consistency between browsers. Granted this isn’t something the Mozilla Foundation can fix, but a new version of the JS language does more harm than good in this context.
Why JS2 is Harmful to Mozilla:
I guess the point is that language syntax is one of the least important features of a platform. Do developers use .Net for C#’s syntax? Is Objective-C’s syntax the reason for Apple’s recent successes? Will the declarative structure of JavaFX Script save the Java platform? I could go on with more examples, but I wont. The answer is a resounding NO! There are much more important things to ensuring the success of a platform than language syntax.
I suppose this doesn’t really need to concern me. The web as a platform will continue to exist and grow and mature. It’s just frustrating to observe this waste of time and energy.
UPDATE: I want to give credit where credit is due. My colleague Josh Gertzen was quoted in AjaxWorld magazine on the irrelevancy of JS2 in an article that ran on Slashdot for a while.