The author mentioned the ES6 problem, which I think is the only valid point made in the whole article (others are way too subjective). Despite the hope that ES

The author mentioned the ES6 problem, which I think is the only valid point made in the whole article (others are way too subjective). Despite the hope that ES6 could be usable as-is, there's always the legacy syntax problem -- and the same applies to coffee-script (and its various forks). Some bad parts of javascript are going to stay in ES6 -- solved beautifully by pre-ES6 coffee, but due to the changes elsewhere we'd have to start over. It remains unclear what we would be using when ES6 gains traction.