JavaScript: The Good Parts
Top Comments
All Comments (155)
-
0:27:30 Closure
alert(digit_name()(3)); // 'three'
-
This guy mentioned HALF OF JAVA SCRIPT as part he won't use anymore because its too dangerous or too risky.
-
Interesting channel. I subscribed just to keep it close on my channel to watch. If you care to subscribe to mine it will be appreciated.
-
I feel your pain, but you have to keep in mind that this was posted in 2009. Much has evolved since then, and much in the favor of HTML5 and JavaScript. The question I have now is what JS framework(s) to use. There's about a bajillion out there (look up TodoMVC on google).
-
um
-
There are IDEs for Lisp and Scheme too, everybody still uses emacs
-
i watched this a couple days ago and now i wanted to use triple equal (===) but did'not work on IE9. So i am back to double equal (==) again. Enough with javascript. It may have good parts but, it has too many bad parts too. Maybe we need something new and powerfull.
-
54min into the video he claims HTML5 and JavaScript are going in a bad direction? I have spend months trying to find the right programming language to learn and a book to go with it. I came up with Head First HTML5 Programming. Now after hearing this I am not sure If I should continue reading this book. I dont want to go in a bad direction with this.
-
0:32:00 - I spent a few hours debugging this.
- Loading comment...
ROFL! Was anyone else kicking themselves hard when he spoke about how JS is the only language people start using without actually learning it? He fucking nailed me on the head right there! Brilliant.
aromanstuff 1 year ago 29
In the 'bad' list, he forgot:
- Debugging closures. A call stack full of anonymous functions is a nightmare.
- IDEs all suck because intelligent code completion is impossible.
jondissed 4 months ago 8