Shameless plug: I put out jsmag in PDF, and regularly get people asking for Kindle version, but have not yet been able to make something look decent. Revisiting this again next month. Suggestions/guidance on this topic welcome.
I had good luck with formatting things for my Kindle with LaTeX. I just set the page size to be proportionate to the Kindle screen and compiled a PDF. The result was far better looking than using the normal Kindle format and I didn't have the normal issues with PDFs because mine actually fit on the screen.
This wasn't the most space efficient system, but it was probably the best one aesthetically. Also, since I just created a custom .sty file to automate this, I can have my single source document output both normal-sized and Kindle-sized PDFs.
I read almost all of my technical books (I've stopped buying technical paperbacks a couple of years ago) on iPad. For whatever reason (natural born cyborg?) my eyes appreciate glowing screen. If only I can make iPad lighter...
I would immediately purchase a DRM free PDF edition of this book, if such were available. I find that's the best format for easily moving between study sessions on my iPad and experimentation on my laptop (e.g. copying code snippets into a REPL or editor).
I've been using node.js since early 2010, but I find it helpful to read books written by a platform's expert developers, as they tend to provide insights and demonstrate helpful patterns of which I was previously unaware.
I'm not interested in buying (and won't buy) a printed copy or a DRM'd digital edition.
I have only read the first two chapters (setup and Javascript an overview).
The content do not look bad (but I have not read node.js specific parts yet so I can't really tell). The bad part is that it would need some serious proof-reading... Some sentences are missing words or are hardly understandable and there are some mistakes in the code.
Reiterating the sentiment. Seems great so far, but there are some errors that could create confusion. The good news is the author left his email address, so I dare say he's well aware by now :)
Just got back into node.js this past week and I think its a great change up from RoR(day job). I'm using the socket.io module and seeing as this guy's responsible for that... I figured I'd support him and order a copy, plus I like reading other perspectives on programming topics. Thanks!
surprisingly enough, I actually saw this book on shelf in person at Barnes and Nobles, just an hour after I saw this post. (the union square location in NYC has it)
I would buy this if there were a PDF version available. Am I able to purchase the Kindle copy and download some kind of Kindle app to read it? I really want this book.
Kindle DRM doesn't annoy me at all. I'm not annoyed by just the existence of some technology, I'm annoyed if this technology hurts my ability to do what I want to do. I do want to read books on iPad, iPhone, Mac, PC and Kindle. I'm able to. If I wanted to steal books I could have been annoyed, but I don't want to.
1984 demonstrated that your ability depends on the continued goodwill and competence of Amazon, who reserved for themselves the power to steal any of your Kindle store purchases.
I like the Chrome reader; it lets you read offline. Also, for programming titles, I actually prefer using a second monitor: more screen than a device, plus ability to copy and paste code is nice.
I would also buy if there were a PDF version. Since my entire library is pdf, I won't install a software and register an account just to read this book.
can anyone tell me if they have found the code error in the tcp-chat in the book. I have run it and I get an error when one telnet session closes. So I assume the error in the conn.on('close') emmitter
51 comments
[ 220 ms ] story [ 1687 ms ] threadAs for the content itself, I'm pretty good with JavaScript, both for the web and for node. Does this add anything new?
Shameless plug: I put out jsmag in PDF, and regularly get people asking for Kindle version, but have not yet been able to make something look decent. Revisiting this again next month. Suggestions/guidance on this topic welcome.
This wasn't the most space efficient system, but it was probably the best one aesthetically. Also, since I just created a custom .sty file to automate this, I can have my single source document output both normal-sized and Kindle-sized PDFs.
I've been using node.js since early 2010, but I find it helpful to read books written by a platform's expert developers, as they tend to provide insights and demonstrate helpful patterns of which I was previously unaware.
I'm not interested in buying (and won't buy) a printed copy or a DRM'd digital edition.
http://eu.wiley.com/WileyCDA/WileyTitle/productCd-1119962595...
The content do not look bad (but I have not read node.js specific parts yet so I can't really tell). The bad part is that it would need some serious proof-reading... Some sentences are missing words or are hardly understandable and there are some mistakes in the code.
http://www.wiley.com/WileyCDA/WileyTitle/productCd-111996259...
There's the Smashing Magazine logo on the upper left hand side of the book.
* On the web or on your iPhone/iPad https://read.amazon.com/
* On Android: https://play.google.com/store/apps/details?id=com.amazon.kin...
PDF is an open standard, the Kindle format is not.
[1]: http://www.nytimes.com/2009/07/18/technology/companies/18ama...
I mean, you can infer what he meant but man it would suck if you didn't know JS that well.
I still applaud this man for his contributions though.