I remember when MicroSoft tried to make it&#x27;s own superscript of JS and people said &quot;Hey this is a bad idea. Standards are a thing for a reason and we should all stick to them.&quot; That argument was correct then and it&#x27;s correct now, IMHO.<p>Where is the objection in 2015? Is it just people are so desensitized by other companies attempts to make JS replacements (that for now compile to JS) that another one just doesn&#x27;t bug anyone?<p>I realize the temptation for big companies like Microsoft with thousands of devs to roll their own, but when every big company abandons standards to focus on their own little alcove we all suffer.<p>And yeah, I realize you can frame it as they haven&#x27;t abandoned the standard because TypeScript compiles to JS and yada, yada. But I disagree. If instead of focusing on TypeScript which you can only take advantage of by working in TypeScript, they focused on libraries for JS that we could all use, I think we&#x27;d all be better off. And that goes for all large corporations that decide to roll their own solutions instead of sticking to standards.<p>Which is not to say JS can never be replaced, I&#x27;d say it&#x27;s long overdue for replacement. But that&#x27;s never going to happen by every big company rolling their own thing. Everybody has to come together.