Uhh, no? I code in JS every day and do nothing of the sort, and I would object if I saw it.
> failing fast is bad and the best reaction to errors is to mess up the page layout in the unexpected way
I don't even know what you mean by this, but the fact that you're conflating JS with "the page" suggests to me that you're not that familiar with server-side JS (which has no "page") and the enormous amount of code that is written to be compatible with it.
If you use Babel you already have that, and just don't know about it. Most "upcoming features" shims do just that.
I don't think so, you can always just use the language in your own style and cherry-pick any tools that align with it.
Like e.g. the Play framework ignored the main standards and idioms of Java development in its day.
Or how every game studio just uses its own version of C++ and forbids tons of features.
It is entirely possible that Javascript itself is an OK language, but it is too late now. The community has already decided that packages should be tiny, that changing prototype of "array" object is an acceptable thing to do, that failing fast is bad and the best reaction to errors is to mess up the page layout in the unexpected way, and so on.
Maybe one day, Javascript will re-invent itself and get reliable software engineering practices. But I highly doubt that -- there are countless people who know the laguage already, and they are not going to be changing their opinions overnight.