So don't use the new features. Nobody is forcing you. Over time, perhaps you will come to appreciate some and bring them into your code. Or perhaps not, both are fine.
Of course, the corollary is to point out that nor should you force your approach on others. Your usage of the language is not the same as everybody else's. They might be working in different contexts to you, solving different kinds of problems to you, with different constraints.
I'd also recommend subscribing to es-discuss. All the features are discussed heavily and repeatedly by experienced, clever people in an open forum, before being standardised and implemented. Only battle-hardened ideas, usually proven in other languages or in JS libraries, make it through the process. There's solid reasoning behind all of them.
I'd like to just clarify one thing - of course everyone can ignore the new features when writing their code, but no one can ignore them when reading other people's code. Undoubtedly, a JS programmer must get a handle on them all, sooner or later.
Thanks for the es-discuss suggestion, it's cool that the process is open like that.
Understanding other people's code is never easy and I get that new language features make it seem even more daunting.
But it is always a useful process to go through, more so when it exposes you to new ideas, patterns and idioms. These features seem intimidating because they are unfamiliar to you, but they won't be unfamiliar forever. I guarantee it.
Wow, that was pretty patronizing! But I think I made a certain argument. You don't have to agree, but it would be nice if you don't just blame it all on my supposed unwillingness to learn new stuff ;)
No, but as someone who doesn't write JavaScript at all, I would like the JS engine that comes with a graphical web browser to be simpler than the expanding spec makes possible. I mostly browse with Lynx anyways, but there's a legitimate concern about how much browser developers are being expected to support here, and what the implications of that are.
Considering the additional syntax is sugar over stuff that is already possible, I'm not sure how much I agree... Anything newer than IE8 can run the transpiled ES5 code that BabelJS/Traceur and others pump out.
Comments
So don't use the new features. Nobody is forcing you. Over time, perhaps you will come to appreciate some and bring them into your code. Or perhaps not, both are fine.
Of course, the corollary is to point out that nor should you force your approach on others. Your usage of the language is not the same as everybody else's. They might be working in different contexts to you, solving different kinds of problems to you, with different constraints.
I'd also recommend subscribing to es-discuss. All the features are discussed heavily and repeatedly by experienced, clever people in an open forum, before being standardised and implemented. Only battle-hardened ideas, usually proven in other languages or in JS libraries, make it through the process. There's solid reasoning behind all of them.
I'd like to just clarify one thing - of course everyone can ignore the new features when writing their code, but no one can ignore them when reading other people's code. Undoubtedly, a JS programmer must get a handle on them all, sooner or later.
Thanks for the es-discuss suggestion, it's cool that the process is open like that.
Understanding other people's code is never easy and I get that new language features make it seem even more daunting.
But it is always a useful process to go through, more so when it exposes you to new ideas, patterns and idioms. These features seem intimidating because they are unfamiliar to you, but they won't be unfamiliar forever. I guarantee it.
Wow, that was pretty patronizing! But I think I made a certain argument. You don't have to agree, but it would be nice if you don't just blame it all on my supposed unwillingness to learn new stuff ;)
No, but as someone who doesn't write JavaScript at all, I would like the JS engine that comes with a graphical web browser to be simpler than the expanding spec makes possible. I mostly browse with Lynx anyways, but there's a legitimate concern about how much browser developers are being expected to support here, and what the implications of that are.
Considering the additional syntax is sugar over stuff that is already possible, I'm not sure how much I agree... Anything newer than IE8 can run the transpiled ES5 code that BabelJS/Traceur and others pump out.