Live data from Hacker News

Learn ES6 and ES7 in 7 Days

getgood.at

11–17 of 17 posts

Re: Learn ES6 and ES7 in 7 Days

#11
IMO, continuing to use the ES6, ES7, ES8 naming is probably going to end up confusing more people. I thought renaming ES6 to ES2015 was a bad idea, since it was already widely used. It would've been better to make the change after ES6. However, going forward, wouldn't it be better to follow along with the ES{YYYY} convention?

For anyone interested in learning about all these newer JavaScript features, I'd highly suggest checking out the JavaScript books by Dr. Axel Rauschmayer [0]. All the books can be read freely, although I'd strongly encourage you to buy em if you find em useful. Before reading Exploring ES6, I thought I knew everything about ES2015, but skimming through it I found tons of things I hadn't been aware of. His books are the gold-standard JavaScript reference.

[0] http://exploringjs.com

Re: Learn ES6 and ES7 in 7 Days

#12

On day 8 you will learn how to use asynchronous code to escape a try/catch block. On day 9 you will learn how to leak memory with closures. On day 10 you will learn how to do unsafe numeric operations with IEEE 754 floating point precision numbers. On day 11 you will learn that the pseudorandom generator in JS is VM specific and may not be secure. On day 12 you will learn to leak memory by binding functions. On day 1…

wow you must be fun at parties! (that is mostly just a pun on your username not meant to convey lots of snark)

anyways lol some of that is too real

jokes aside I think web development has come a long way and JS gets a bit of a bad rep. Full stack JS is insanely productive as a stack when you consider what you can build with it. It might be buggy and make you say "wat?" a lot but in exchange you can build insanely complex apps in timeframes that used to be the stuff of dreams. Granted many times what we build has no need to be so insanely complex, but when we really need it JS is there to make complicated things just magically easy to build.

Re: Learn ES6 and ES7 in 7 Days

#13

Looks nice - and the font! ;) On a more serious note, I know ruby, but I really want to learn JS - is this a good place to start? Or, is there a better place to start, and then come back here?

As I commented on the parent [0], I'd suggest checking out the JavaScript books by Dr. Axel Rauschmayer! In addition to learning about the language, he also published Setting up ES6, which covers how you'd go about setting up your environment in order to target node and browsers that support ES5.

[0] https://news.ycombinator.com/item?id=14105020

Re: Learn ES6 and ES7 in 7 Days

#14
post #12

On day 8 you will learn how to use asynchronous code to escape a try/catch block. On day 9 you will learn how to leak memory with closures. On day 10 you will learn how to do unsafe numeric operations with IEEE 754 floating point precision numbers. On day 11 you will learn that the pseudorandom generator in JS is VM specific and may not be secure. On day 12 you will learn to leak memory by binding functions. On day 1…

wow you must be fun at parties! (that is mostly just a pun on your username not meant to convey lots of snark) anyways lol some of that is too real jokes aside I think web development has come a long way and JS gets a bit of a bad rep. Full stack JS is insanely productive as a stack when you consider what you can build with it. It might be buggy and make you say "wat?" a lot but in exchange you can build insanely com…

I think all technologies have sharp edges somewhere, and the way to stay afloat in this business is staying alert.

Testing assumptions help, be it through quick REPL experimentation or a unit test.

JavaScript has some bad fame around unintuitive behavior but you can find these styles of issues in most languages. A random example: Scala. https://www.youtube.com/watch?v=uiJycy6dFSQ

Re: Learn ES6 and ES7 in 7 Days

#15

IMO, continuing to use the ES6, ES7, ES8 naming is probably going to end up confusing more people. I thought renaming ES6 to ES2015 was a bad idea, since it was already widely used. It would've been better to make the change after ES6. However, going forward, wouldn't it be better to follow along with the ES{YYYY} convention? For anyone interested in learning about all these newer JavaScript features, I'd highly sugg…

Thank you!

I'd seen these posted before and remember thinking how good they looked and then promptly forgot enough I've not been able to find them again.

Re: Learn ES6 and ES7 in 7 Days

#17
post #12

On day 8 you will learn how to use asynchronous code to escape a try/catch block. On day 9 you will learn how to leak memory with closures. On day 10 you will learn how to do unsafe numeric operations with IEEE 754 floating point precision numbers. On day 11 you will learn that the pseudorandom generator in JS is VM specific and may not be secure. On day 12 you will learn to leak memory by binding functions. On day 1…

wow you must be fun at parties! (that is mostly just a pun on your username not meant to convey lots of snark) anyways lol some of that is too real jokes aside I think web development has come a long way and JS gets a bit of a bad rep. Full stack JS is insanely productive as a stack when you consider what you can build with it. It might be buggy and make you say "wat?" a lot but in exchange you can build insanely com…

> It might be buggy and make you say "wat?" a lot but in exchange you can build insanely complex apps

Insanely complex apps on a buggy foundation? What could possibly go wrong...

Post reply on HN