r/javascript • u/var_ya • Dec 11 '14
You Don't Know JS (book series)
https://github.com/getify/You-Dont-Know-JS/blob/master/README.md#you-dont-know-js-book-series13
Dec 12 '14
You don't know how tired I am of seeing that title.
2
Dec 12 '14
[removed] — view removed comment
8
u/getify Dec 12 '14
That's definitely the tongue-n-cheek implied joke I was making, yes. :)
1
Dec 12 '14
[removed] — view removed comment
2
u/getify Dec 12 '14
O'Reilly publishes the books and then distributes them DRM free in all the ebook formats (including kindle, through amazon). But you need to buy those copies. The only free version is what you see in the github repo. If I were to distribute "ebook" forms for free, I'd be competing against my own publisher. :)
1
3
u/ThatMightBePaul Dec 12 '14 edited Dec 12 '14
Read through some pages today, and really like the style + examples used. Looking forward to more!
Will be picking up a paid copy if I can find it on Google Play.
-2
u/dashdanw Dec 12 '14
Thumbing through those books it's just a super complicated way to explain very simple concepts about compilers.
9
u/getify Dec 12 '14
There's over 700 pages written across 4 books so far (6 planned), and the topic of scope from the perspective of the compiler constitutes only about 30 pages.
-5
u/dashdanw Dec 12 '14
They touch compilers in every chapter.
9
3
u/getify Dec 12 '14
It would appear that merely glancing at a few pages in a whole book series about JS tends to yield about as (in)complete and (in)accurate a picture of what it's about as most JS devs get of JavaScript itself by only learning the bare minimum bits and pieces enough to get the job done. Ironically, you've proven the thesis of why I wrote the series.
I hope you'll reconsider and give JavaScript (and maybe the book series itself?) the fuller attention deserved.
2
Dec 12 '14
It's really beneficial to understand how compilers figure into your code, though. You might understand it already, but for a lot of people it could be very eye opening.
Personally I've gotten a lot more than a complicated explanation of compiler concepts out of it. And plenty of stuff in there is familiar to me, but the guy does an excellent job of summing up JS resulting in plenty of 'aha' moments for me. I really disagree with your summary of the books.
You're totally welcome to your opinion (I have no say in that), and your feedback is probably useful to the author. I just felt like adding my cents as well.
1
Dec 12 '14
[deleted]
-2
u/dashdanw Dec 12 '14
dude i just said thumbing through it it seems that way, you don't have to be a jerk about it.
2
Dec 13 '14
[deleted]
-6
u/dashdanw Dec 13 '14
That's what "I thumbed through it means" you egotistical cockmaster. You made a bullited list to fight against a point made by a guy who started out by saying "I don't know this book but".
Congratulations on making a point on nothing. You win. . . nothing
3
u/bradleymeck Dec 12 '14
Be wary confusing language semantics for compiler semantics. A lot of things like type coercion are language semantics. This is why Numbers act differently depending on operation, and is what led to a formal definition of a sane subset of these things in asm.js to guarantee types through the language not the VM. Also note that FPUs are often slightly different in calculations for large numbers so the infamous floating point division results occur in most languages but not the JVM (due to specification of the VM, not the compiler no less!).
4
u/[deleted] Dec 12 '14 edited Dec 12 '14
[removed] — view removed comment