TypeScript as a transpiler instead of Babel?

Question

JavaScript

It was in the evening. there was nothing to do ... ) in general, I dug a little into typescript and was surprised to find that it can be used, like Babel, as a transpiler from es6 / 7 to es5, and I definitely liked the compiled ts code more . In addition to the fact that the code turned out to be cleaner and smaller - there are no terrible Babel helpers, TS also supports features that are not in babel - for example, array comprehensions (they were removed from babel).
Which tool as a transpiler (that is, the features of TS itself are not yet of interest) for the web frontend is more preferable - Babel or TypeScript ? I would like to see the pros and cons of both technologies.
The number of stars and contributors on the github is relatively the same, but there is a large corporation behind TS (although the development itself is open). And this is not taking into account the features of TS itself and the upcoming Angular 2.

Answer 1

Babel follows the standard, if something changes in the standard, babel also changes, the whole point is that when a new feature is fixed in the standard and introduced on target environments, you can safely stop using babel and everything will work
TypeScript is a separate language transpiled in js, yes, it is very close to js itself (unlike, say, coffee), but in most cases you will never refuse a transpiler