5 ms·
so how is this different from say TypeScript?
by albeva 12y ago
so how is this different from say TypeScript?
- itsbits 12y agoonce browsers/JS engines supports ES6/ES7, we don't need babel. But thats not the case with Typescript. But we never know. Babel may start supporting ES8. It can be never ending process.
- deleted 12y ago[deleted]
- stupidcar 12y agoI'm sure Babel will be supporting ES8 and beyond. The rename wasn't just about ES6/ES7 confusion, I believe, but to reflect the expanded ambition of the project to be a general transpiler from the edge ES version to the version with the widest browser and Node.js/io.js support. However, TypeScript's goals aren't as different as you might think. It is a strict superset of JavaScript, and although it adds features that are not yet on the standards track, there are proposals to add optional static typing via annotations to JS. Given that Google are also interested in such a capability, given Dart and AtScript, it seems probable that types will eventually become part of the language.
- itsbits 12y agoagreed. But don't think Dart will last long considering Angular community went for a new AtScript over Dart...Also I am preferring to use Babel is in future I can remove that dependency which not the case with TypeScript or AtScript..
- thomasfoster96 12y agoTypescript is a language that compiles to javascript, adding some features. 6to5 (now Babel) compiles javascript with Ecmascript 6 and 7 features (poorly supported) to JavaScript code that only uses Ecmascript 5 features (which all major browsers since 2011 have supported).