3 ms·
I really don't get the arrogant "You don't know X". Maybe I know it, maybe I don't know it. But if I know it already, then I am wasting my time since I think I
by franciscop 10y ago
I really don't get the arrogant "You don't know X". Maybe I know it, maybe I don't know it. But if I know it already, then I am wasting my time since I think I don't know it (not really). However if I don't know it, then the condescending tone doesn't really motivate me to want to know (while I love to learn about Javascript).
- rankam 10y agoI always assumed it was a play on the game You Don't Know Jack, but I could be wrong. https://en.wikipedia.org/wiki/You_Don%27t_Know_Jack_(video_game_series) https://en.wikipedia.org/wiki/You_Don%27t_Know_Jack_(video_g...
- ZeroGravitas 10y agoI had assumed it was a play on the slightly ruder version "You don't know jack-shit" as JS works as an abbreviation for both.
- petercooper 10y agoIt's just a catchy, challenging title, a la "Learn X The Hard Way" or "X For Dummies".
- doomtop 10y agoI do think it is meant to be a catchy marketing play on "You Don't Know X" but the author also describes it as a reference to the fact that "knowing" JavaScript can only ever be temporal: No matter how much you feel you've mastered JavaScript to this point, the truth is that JavaScript is never going to stop evolving, and moreover, the rate of evolution is increasing rapidly. This fact is almost a metaphor for the spirit of this series, to embrace that we'll never fully know every part of JS, because as soon as you master it all, there's going to be new stuff coming down the line that you'll need to learn.[1] [1] From Ch. 3 "Into YDKJS" of the first book Up & Going: https://github.com/getify/You-Dont-Know-JS/blob/master/up%20&%20going/ch3.md#es6--beyond https://github.com/getify/You-Dont-Know-JS/blob/master/up%20...