[badminton1]

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 13 you will learn to add timeouts to asynchronous operations so they don't last forever.

On day 14 you will learn what the floating point epsilon is and how number comparisons are unreliable.

[k2052]

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.

[badminton1]

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

[PerfectDlite]

> 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...