How do I learn JavaScript with its modern features is best?

>>60736354
Look for ES6 tutorials.

File: ee2913a810c3736da6a853f1880d21d9.jpg (641KB, 700x1060px) Image search: [Google]

641KB, 700x1060px

>>60736354
>dye your hair purple
>Get a macbook
>download atom and make sure you have all the useless plugins like text blur
>go to a starbucks and get a pumpkin spice latte
>profit

>>60736354
You don't want to use ES6 unless you're gonna be writing node for backends or for electron applications.
Most end users are running outdated browsers that don't even support the "use strict;" directive.

>>60736417
>chrome is the most used browser on the internet
>safari is second
>chrome auto updates every time you start it up
>safari has full es6 support for over two years
okthen.

>>60736354

Just do some random tutorial to learn the "old" JS. And then learn the new ECMA6 features on top.


>>60736434


>chrome is the most used browser on the internet
>safari is second

While the bottom line of your post is true (you can use ECMA6 today), this specific claim is problematic:

Chrome is the "most used" browser, because of the Android phones identifying itself as "chrome".

Same for iPhone and Safari.

But if you look only at desktop, Firefox is where it's at.

>>60737083
>But if you look only at desktop, Firefox is where it's at.
Firecucks are delusional.

>>60737083
I'm a huge Firefox user and fan but >>60737097 is right. Firefox's market share is laughably small, hardly anyone uses it anymore unfortunately.

>>60736417
You can use it with Babel. Even features not yet supported by Chrome.

>>60736417
You can use webpack or babel to compile to ES5 with map files and debug it in any modern browser. Or you can tell IE users to fuck off and come back with a modern browser.

>>60737083
I know of only one person using Firefox on desktop. This browser is outdated on every level. Slow JS, battery hog, half-working multiprocess, no decent sandboxing, slow in general. No one uses it.

>>60737305
It was worth using it for Firebug but they killed and replaced it.

>>60737083
And those mobile browsers support ES6 as well, so whatever you're trying to say here is incorrect.