Skip to content

Comment on ES6 in Depth: Destructuring

Comments

The part of this that is disengenuous and a little silly is that they are just slowly adding in features from CoffeeScript/IcedCoffeeScript and nobody mentions that.

And in order to do it you have to use something like Babel.

Why not just move to CoffeeScript, or IcedCoffeeScript, or ToffeeScript, or even LiveScript?

The only explanation I can see is that people just aren't capable of learning the full new languages and so the standards people are leading you by the hand like you just got off the short bus.

AND, the standards people don't want to admit that individuals did their jobs for them years ago, don't want to use someone else's design for implementing those features and so insist on slowly coming up with their own independent implementations for engines.

This is a microcosm that demonstrates the relationship between technology and society. There is just a huge lag between the newest and best ideas or systems and what the group or individuals or systems can grasp or absorb.

Take this existing many-year gap and multiply by 10X or 100X and you will start to perhaps understand the concept of the technological singularity.

The standards people very often are the same people, or represent the same organizations, that implemented the features in other places ahead of it being standardized as part of ES.

AboutSource Built by g1lg1l

Hackerly is an independent reader for Hacker News, built on the public HN API. Not affiliated with Y Combinator.