|Written by Ian Elliot|
|Thursday, 26 March 2015|
It was a twist of Internet fate that Eich was not one of the Java or C++ is the way to go people and so he invented something different - a language that was functional and object-oriented where functions were first class objects and objects were associative arrays or hashes depending on your terminology. This made his language different and misunderstood, a status it retains to this very day.
Whatever the reason, you have to agree with Brendan Eich:
"ECMAScript was always an unwanted trade name that sounds like a skin disease."
With the latest version of ECMAScript you might think that there is a chance for putting things right - but no, things are getting worse.
What has now happened is that the ECMAScript community has decided to switch to year numbering. So it isn't going to be ES6, but ES 2015.
What other language conforms to a standard of a language with a different name?
OK, I'm sure you could find me one, but you get the point.
What corresponds to www.python.org, www.ruby-lang.org, php.net, golang.org or even isocpp.org?
The best we have is MDN, which covers just one dialect of the language that isn't quite ECMAScript.
What is the solution?
This isn't going to happen.
To be informed about new articles on I Programmer, install the I Programmer Toolbar, subscribe to the RSS feed, follow us on, Twitter, Facebook, Google+ or Linkedin, or sign up for our weekly newsletter.
or email your comment to: email@example.com
|Last Updated ( Thursday, 26 March 2015 )|