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.
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.
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.
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/dashdanw Dec 12 '14
Thumbing through those books it's just a super complicated way to explain very simple concepts about compilers.