5 ms·

Dart is for Google, by Google, and external engagement has been as neglected as for all of Google's front end efforts. Google ceded the thought leader position

Dart is for Google, by Google, and external engagement has been as neglected as for all of Google's front end efforts. Google ceded the thought leader position in this area years ago and everybody knows better than to trust any of their new efforts.

tkubacki 9y ago
So this is official reason why it was not considered ?
- vmarsy 9y ago
  I don't know, but the reddit blog post says: > One of the worries we had with Flow was that it was built to solve specific needs at Facebook and that its future would be determined by that scope. if you replace [Flow/Facebook] with [Dart/Google] , I guess you could make the same point.
  - wereHamster 9y ago
    If you look through the flow source code then you'll find many facebook-specific features. Search for 'Facebookism'! I don't know about Dart. But TypeScript is written primarily for the community, not for Microsoft.
noway421 9y ago
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 main adopter of typescript.
- 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.

tkubacki 9y ago

So this is official reason why it was not considered ?

vmarsy 9y ago
I don't know, but the reddit blog post says: > One of the worries we had with Flow was that it was built to solve specific needs at Facebook and that its future would be determined by that scope. if you replace [Flow/Facebook] with [Dart/Google] , I guess you could make the same point.
- wereHamster 9y ago
  If you look through the flow source code then you'll find many facebook-specific features. Search for 'Facebookism'! I don't know about Dart. But TypeScript is written primarily for the community, not for Microsoft.

noway421 9y ago

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 main adopter of typescript.

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.