4 ms·

There's still polymer which is developed by chrome team and angular2 by ads department and those seem to be quite industry proven. E.g. angular2 is one of the m

• JeremyBanks 9y ago
  Don't forget that Google's first instinct for Angular 2 was to create an incompatible fork of TypeScript. https://en.wikipedia.org/wiki/AtScript https://en.wikipedia.org/wiki/AtScript
  • TomMarius 9y ago
    That was because TypeScript didn't support decorators back then - the "at" comes from the at sign.
    • JeremyBanks 9y ago
      Yes, and what kind of reasoning is that? You do not fork a language to make your framework a little more convenient. It's inane. That's how you end up with both a dead language, and a dead framework. Microsoft saved them from themselves. (I expect they could have arranged to have the feature added without first publicly declaring their intention to fork the language, but that's above their community engagement skill level.) Google's Closure Compiler was the best version of compiled JavaScript for five years. It should have been the winner, but Google did nothing to make it palatable to the open-source community (docs are a disaster, the code is full of unexplained Google-specific workarounds, it integrates with nothing), got trampled, and now they're forced to adopt someone else's tech to remain relevant. Google is so bad at this.