Why did the Angular team choose TypeScript over Dart?

The article explains that Angular’s move toward TypeScript grew out of the Microsoft-Google collaboration and the end of AtScript. It presents TypeScript as a choice that fits the existing Angular user base, while Dart is described as harder to adopt inside current JavaScript workflows.

Reading notes

#

• The Microsoft-Google partnership led Angular 2.0 to adopt TypeScript instead of AtScript.
• TypeScript matches the skills of existing web developers because it stays close to JavaScript.
• Dart is presented as less direct for developers who already work in JavaScript.
• A criticism of Dart is that its interop layer can keep projects siloed on the Dart platform.
• Another issue is that Dart does not currently produce consumable JavaScript in the same way TypeScript does.
• TypeScript is described as a typed superset of JavaScript, so existing JavaScript projects can move over by renaming source files from .js to .ts.
• The article also says Dart could work better if it existed alongside JavaScript and compiled to readable, fast JavaScript.
• The interop library is presented as a possible way for Dart developers to use existing JavaScript libraries.