Great article!
It would be fantastic to make all the code snippet interactive with the klipse plugin.
http://blog.klipse.tech/javascript/2016/06/20/blog-javascrip...
Overview of JavaScript ES6 features
221–230 of 250 posts
Re: Overview of JavaScript ES6 features
#222Earlier quoted context omitted.
You know instead of: const getObj = (id, store) => { return { id } } You could write: const getObj = (id, store) => ({ id })
I'm pretty sure that's a good illustration of my point.
This is a matter of personal preference.
I find `return` to be quite distracting and annoying for a small function that spans part of a line, while you and some others may prefer the explicitness of the `return` keyword.
I would agree that nested destructuring should be used quite cautiously. Code legibility is incredibly important to the success of any serious project.
Re: Overview of JavaScript ES6 features
#223"you can start using it right now" if you don't care about IE8, IE9, IE10, and many mobile browsers and are willing to ignore 20% of your customers. e.g: http://caniuse.com/#search=let const does not have block scope in those browsers either, but will work, adding to your debugging confusion. template literals and multiline string has no IE support at all (you need edge: https://developer.mozilla.org/en-US/docs/Web/J…
We use Babel to compile ES6/ES7/ES8 to ES5. https://babeljs.io
It's not what the article is about. The article is obviously talking about native ES6 features, otherwise it would advertise es7 features as well and advise to use transpilers.
Re: Overview of JavaScript ES6 features
#224Earlier quoted context omitted.
> Is it just me, or is Javascript (and more generally, all front end technology) more susceptible to these trivial holy wars? - Tabs vs spaces. - Vi vs Emacs - Weak vs strong typing - where to place {} in block statements - where to put commas No, programming in general is susceptible to these trivial holy wars.
Vi vs Emancs? Weak vs strong typing?? tabs vs spaces??? where did you get those?? The ONLY holy war in JS is the semi-colon one
Clearly you have never encountered the strange "comma first" brigade.
Re: Overview of JavaScript ES6 features
#225Earlier quoted context omitted.
> Is it just me, or is Javascript (and more generally, all front end technology) more susceptible to these trivial holy wars? - Tabs vs spaces. - Vi vs Emacs - Weak vs strong typing - where to place {} in block statements - where to put commas No, programming in general is susceptible to these trivial holy wars.
We have a little more than vi and emacs these days as competition not two sided wars.
Sublime vs Atom if you prefer.
The point still stands
Re: Overview of JavaScript ES6 features
#226Earlier quoted context omitted.
> Is it just me, or is Javascript (and more generally, all front end technology) more susceptible to these trivial holy wars? - Tabs vs spaces. - Vi vs Emacs - Weak vs strong typing - where to place {} in block statements - where to put commas No, programming in general is susceptible to these trivial holy wars.
Vi vs Emancs? Weak vs strong typing?? tabs vs spaces??? where did you get those?? The ONLY holy war in JS is the semi-colon one
Though I don't see why this is a holy war in the first place. Clearly, no-semicolon is the only way to go.
:^)
Re: Overview of JavaScript ES6 features
#227"you can start using it right now" if you don't care about IE8, IE9, IE10, and many mobile browsers and are willing to ignore 20% of your customers. e.g: http://caniuse.com/#search=let const does not have block scope in those browsers either, but will work, adding to your debugging confusion. template literals and multiline string has no IE support at all (you need edge: https://developer.mozilla.org/en-US/docs/Web/J…
> "20% of your customers"
Depends on the product.
Regardless, you can easily transpile a codebase to support those browsers.
If you aren't doing that already, you probably should be. Otherwise you're supporting a codebase that is quickly going to become very dated and (in comparison to a more modern codebase) much messier.
Re: Overview of JavaScript ES6 features
#228Earlier quoted context omitted.
Vi vs Emancs? Weak vs strong typing?? tabs vs spaces??? where did you get those?? The ONLY holy war in JS is the semi-colon one
Clearly you have never encountered the strange "comma first" brigade.
Au contraire, for a while I was one of them. But I think we were seen as too weird to even bother with a holy war
Re: Overview of JavaScript ES6 features
#229Earlier quoted context omitted.
Vi vs Emancs? Weak vs strong typing?? tabs vs spaces??? where did you get those?? The ONLY holy war in JS is the semi-colon one
Though I don't see why this is a holy war in the first place. Clearly, no-semicolon is the only way to go. :^)
[loads machine gun...]
Re: Overview of JavaScript ES6 features
#230Earlier quoted context omitted.
Vi vs Emancs? Weak vs strong typing?? tabs vs spaces??? where did you get those?? The ONLY holy war in JS is the semi-colon one
That's what OP is saying: programming has plenty of holy wars that predate JavaScript.
You are right, I misread his comment