Monday, April 13th, 2009
Now we have a final release of that work, with a new name, EcmaScript Edition 5 which is an interesting change :)
Erik Arvidsson tells us his thoughts:
The most exciting thing in ES5 is that it finally standardize getters and setters. It also allows us to control the enumerability as well as whether properties should be read only etc. ES5 also adds a few other things like the array extras from Mozilla.
Yes indeed. We now have things like
Function.bind. Well, by “now” we mean “when browsers support this.”
For the average web developer the release of a candidate specification has little immediate impact because you have to create content that works with the browser versions that are actually in use today. However, we expect that once it is finally approved, the revised ECMAScript standard to be widely and fairly rapidly adopted by browsers. In the meantime, this new specification is already having an impact. For example, in IE8 both the native JSON and the DOM Prototypes features are based upon APIs defined in the ECMAScript Fifth Edition Specification.
An interesting glimpse into the Microsoft developer world can also be found by checking out the comments to that entry:
I think it makes immense sense to hold off a final release of Managed JScript until the fifth spec is finalized, but the complete lack of transparency in the Managed JScript process has been a little disconcerting. When Managed JScript was announced it was promising, but IronPython and IronRuby have completely eclipsed it. Whether in the DLR for Silverlight or ASP.Net futures, Managed JSCript has been intentionally hidden, which is a shame.
On the other hand, this is hardly enough change. Getting a couple of the useful Prototype methods like bind, and some nice Array helpers and the like…. good to get us all on the same page, but come on guys, it’s time to step it up a notch! Harmony here we come :)
Posted by Dion Almaer at 8:01 am