This is an annotated version of the second edition of <a href="http://eloquentjavascript.net/" rel="nofollow">http://eloquentjavascript.net/</a>.<p>There are two objectives for this project:
(1) Add comments to make the text easier to understand.
(2) Allow you to ask me questions using comments so you don't get stuck.<p>The big idea is that you’ll be able to get through the book without any issues and understand everything on a very deep level. I’ve heard from too many people that the first few chapters have been smooth and then the middle to later chapters have been a struggle (which is a big shame). I want the entire book to be a smooth experience so that you can feel confident about JavaScript and can move on to bigger things.<p>My goal is to create a really useful and lasting resource that helps a ton of people. Please let me know what you think!<p>If you've struggled through parts of the book before, I'd love to hear about it so that I can spend more energy on the parts where you need it most.<p>I also posted this on Reddit and it's currently at the top of /r/learnjavascript if you'd like to see the discussion there.
<a href="http://www.reddit.com/r/learnjavascript/" rel="nofollow">http://www.reddit.com/r/learnjavascript/</a>
People keep voting this up, even though the comments are broken. If you're just going to read the book, note that there's a better-formatted, interactive version at <a href="http://eloquentjavascript.net" rel="nofollow">http://eloquentjavascript.net</a>
I haven't been able to see the comments so I can't give feedback on that, but you should give proper credits to the book's author, Marijn Haverbeke and respect his choice of license, <a href="http://creativecommons.org/licenses/by-nc/3.0/" rel="nofollow">http://creativecommons.org/licenses/by-nc/3.0/</a> (summary) and <a href="http://creativecommons.org/licenses/by-nc/3.0/legalcode" rel="nofollow">http://creativecommons.org/licenses/by-nc/3.0/legalcode</a> (full license).
It's a great and well written book already. I'm not sure how can you benefit from annotating it any further.
It's important to accept that some books are aimed at a certain level and for people not quite there yet better alternatives exist [1]. There are also some topics that a book needs to just mention and not go into much details, because for a beginner the exact internals of TCP are not useful anyway.<p>[1] <a href="http://jsbooks.revolunet.com/" rel="nofollow">http://jsbooks.revolunet.com/</a>
I just bought this book last week and havent dove in yet. Bookmarking this page for future reference.<p>Can anyone suggest a JS book to read after this one, for someone thats not quite a beginner with programming but trying to improve their JS skill set?
> "Below the surface of the machine, the program moves. Without effort, it expands and contracts. In great harmony, electrons scatter and regroup. The forms on the monitor are but ripples on the water. The essence stays invisibly below."<p>Man, I hate reading stuff like this in technical books.
This would probably not be trivial, but perhaps it would be better to upload this to Github in Markdown format? Github would allow comments, suggested changes to the original text, version control, etc.