What prospects do you see in the development of js "wrappers"?

Question

JavaScript

The question is primarily for those who practice "wrappers" in their work.
At the moment, there are a number of "wrappers" around javascript that have been brought to the stage of industrial implementation. Such as: typescript, jsx, coffescript, dart(? not sure if it should be listed with the rest) they all have their advantages for sure (I didn't go beyond a little experimentation with any of them), but don't they as a result, a monstrous "something" from hitherto a language with low entry thresholds, interpreted, dynamic typing, prototype model and a sufficient level of syntactic sugar.
I understand why it was "ported" to the server (node.js, io.js), but somehow I don't see "deadly flaws" in it
Actually the question is: what do you see as the advantages of the listed and other add-ons / wrappers, which one do you think is the most promising and why (here angular 2 will be on typescript, for example)?
Also, of course, your general thoughts on the topic are interesting.

Answer 1

In my understanding of preprocessors, the niche for coffescript is occupied by those who prefer the ruby ​​philosophy.
In the direction of typescript, those who have moved from typed languages ​​and at the
moment cannot imagine how you can make a large application without programming
"on interfaces", which is the philosophy of typed languages, are looking towards typescript.
Babel fans, this is the third side of the force that is now learning about the future.
Personally, I looked at coffe and I liked the compiled code less than the clean as a tear,
compiled typescript code.
And I settled on Babel, because js is poor without the latest innovations, and choosing between writing an entire library or using exactly the same plus learning tomorrow's syntax, I chose the latter.

Answer 2

Wrappers (CoffeeScript in particular) turn your beautiful Javascript code into monstrous Perl-like disgusting shit, disgusting syntax. Someone like...

Answer 3

I use hax. haxe.org
You can write applications for different platforms.

Answer 4

None. All of them have two goals:
But they only harm the owners of sites - it is then impossible to fully support it. And as far as SEO is concerned, there is a pipe in general ...

Answer 5

languages ​​with low entry thresholds

Hoho, low? That's what people come to an interview and can't say a word about JS.
I'm currently using ES6 as the future of JS. I plan to use TypeScript as soon as Angular2 comes out. Maybe earlier, but so far too lazy.
The benefits are banal - less code, everything boring is generated. The sweetest things for me personally are arrow functions, sugar over the declaration of their types (like classes), procs and wikimaps and modules as the main feature that I use.
From typescript, I'm only interested in describing types for variables and arguments/return values. Annotations are possible.

Answer 6

Very controversial is the case such wrappers. Firstly, compilation is required for use, and secondly, code support and developer interchangeability become more complicated. Angular may fall out of favor due to the need for wrappers. Something really good will eventually be introduced into regular js - moreover, in a more convenient and thoughtful form.