3 ms·
> but could 1) be implemented in a transpolar Why is that an argument against a new feature? Should we stop developing transpilable features? This creates frag
by nawitus 11y ago
> but could 1) be implemented in a transpolar
Why is that an argument against a new feature? Should we stop developing transpilable features? This creates fragmentation and a jungle of compile-to-JavaScript languages order of magnitude bigger than what we've got now. The more languages you have the more effort is required for having good tooling, which is already lacking.
> unfortunately behave different with regard to this and thus make the language even harder to understand
In my opinion they make the language more easier to understand, as the this keyword becomes rarely required, the code becomes more readable and you'll get rid of weird var that = this; or .bind tricks.
> Classes are horrible in my opinion
Classes are pretty nice. It's a syntax sugar which is nicer and easier to understand than using functions and prototypes.
> Let scope is fine I guess, I honestly never thought this was a big deal
It eliminates a certain class of bugs without a downside. I never use var anymore.
I agree with the general point that ES6 seems to have focused a lot on not that important syntax sugar.
- johnmaguire2013 11y ago> Classes are pretty nice. It's a syntax sugar which is nicer and easier to understand than using functions and prototypes. I actually think that this syntax sugar is the opposite of a solution. It has always been tricky getting developers coming in from other languages (mainly C-like, and Java-like) to understand that JS is NOT an object-oriented language, but in fact is a prototypal language. By adding the class keyword, I think this only confuses those users further.
- paublyrne 11y agoIt has always been tricky getting developers coming in from other languages (mainly C-like, and Java-like) to understand that JS is NOT an object-oriented language, but in fact is a prototypal language. It's both.