Why is ECMAScript still not a W3C recommendation?

In theory, browsers can support multiple programming languages ​​for client-side web page scripts. In practice, ECMAScript is the only one widely deployed and used in all browsers. Therefore, for most people it is an integral part of the Internet.

However, it was never advertised as a W3C recommendation for writing web pages. And HTML5 seems to be promoting it, even though client-side interactivity is becoming more and more important. Why is this so?

  • Is a monopoly in a programming language on a web platform possible? (obviously failed)
  • Is it because the W3C prefers to concentrate ONLY on the declarative side of the Internet?
  • Or just a political position?
+5
source share
1 answer

I'll take the bang: W3C is trying to develop and recommend standards. ECMAscript is already a standard from ECMA. He does not need to re-ratify the language.

Something close to this is w3c's attempts to standardize a Document Object Model (DOM) model, with which all browsers interact with an HTML page using javascript / ecmascript (or vbscript or any other client-side scripting language). It wasn't really tbh swimming, but it's better than nothing (so they keep telling me)

http://www.w3.org/DOM/

-Oisin

+8
source

All Articles