Re:Smashing Node.JS book is out.
by DigitalSea on Sunday September 16, 2012 @05:35PM
(#4530459)
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.
Re:Smashing Node.JS book is out.
by bdcravens on Sunday September 16, 2012 @10:26PM
(#4531111)
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.
Re:Smashing Node.JS book is out.
by kika on Sunday September 16, 2012 @06:29PM
(#4530600)
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.
Re:Smashing Node.JS book is out.
by prodigal_erik on Sunday September 16, 2012 @07:33PM
(#4530758)
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.
Re:Smashing Node.JS book is out.
by m-i on Sunday September 16, 2012 @05:57PM
(#4530514)
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.
Re:Smashing Node.JS book is out.
by mgkimsal on Sunday September 16, 2012 @05:35PM
(#4530457)
And I've been wary about publishing them :)
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.
Re:Smashing Node.JS book is out.
by tikhonj on Monday September 17, 2012 @03:39AM
(#4531617)
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.
Re:Smashing Node.JS book is out.
by kika on Sunday September 16, 2012 @05:51PM
(#4530498)
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...
Re:Smashing Node.JS book is out.
by cjstewart88 on Sunday September 16, 2012 @04:34PM
(#4530245)
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!
Re:Smashing Node.JS book is out.
by michaelsbradley on Sunday September 16, 2012 @03:56PM
(#4530159)
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.
Re:Smashing Node.JS book is out.
by cirotix on Sunday September 16, 2012 @06:57PM
(#4530675)
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.
Re:Smashing Node.JS book is out.
by kyebosh on Monday September 17, 2012 @01:25AM
(#4531403)
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 :)
Re:Smashing Node.JS book is out.
by kfrank on Monday September 24, 2012 @01:53PM
(#4565979)
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
Re:Smashing Node.JS book is out.
by zemo on Sunday September 16, 2012 @05:26PM
(#4530422)
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)
* 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...
As 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.
http://eu.wiley.com/WileyCDA/WileyTitle/productCd-1119962595...
http://www.wiley.com/WileyCDA/WileyTitle/productCd-111996259...
There's the Smashing Magazine logo on the upper left hand side of the book.
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 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.
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.