- Paperback: 148 pages
- Publisher: Pragmatic Bookshelf; 1 edition (December 5, 2013)
- Language: English
- ISBN-10: 1937785734
- ISBN-13: 978-1937785734
- Product Dimensions: 7.5 x 0.3 x 9.2 inches
- Shipping Weight: 12 ounces (View shipping rates and policies)
- Average Customer Review: 4.1 out of 5 stars See all reviews (68 customer reviews)
- Amazon Best Sellers Rank: #164,425 in Books (See Top 100 in Books)
Enter your mobile number or email address below and we'll send you a link to download the free Kindle App. Then you can start reading Kindle books on your smartphone, tablet, or computer - no Kindle device required.
To get the free app, enter your mobile phone number.
Use the Amazon App to scan ISBNs and compare prices.
Prepare for your professional certification with study guides and exam prep tools from Wiley. See more
Frequently bought together
Customers who bought this item also bought
"If you’re just getting started with Node, skip everything else––this is the only book you’ll need."
"Finally, a book that teaches that Node.js is much more than a bare-bones webscale application server for hipsters."
About the Author
Jim R. Wilson is a software engineer at Google. He's contributed to several open-source projects including corridor, HBase, MediaWiki, and Node.js. In addition to coding and writing, Jim is a speaker and co-author of Seven Databases in Seven Weeks.
Browse award-winning titles. See more
If you are a seller for this product, would you like to suggest updates through seller support?
Top Customer Reviews
I bought the book based on good reviews, but I'm feeling a bit dumb for not digging deeper. Yes, it has helped me learn node somewhat, but I feel there are better resources currently. If the author would release an update, the book could regain its former glory.
So the author, after getting the basics down, suddenly decides to use zmq module, which is where the problems start. The book is more interested in multi-threading and network connections of kinds that 90% of us will never care about, given that MEAN is the vast majority of node use (not the only just the most common). So the following chapters, starting at 4 but continuing through 5 and more will require things that for many of us won't work - not without serious administrator support, and the fixes are NOT the same from user to user - the internet is flooded on technical sites with issues about node-gyp builds (of native modules that use it) failing for all kinds of reasons, and it's often 10 different fixes suggested, often none work for most posters of the threads. SO I can't recommend this book because it's not a book on node but on Jim Wilson's wish list of how the rest of use should find node easy to use - it isn't.
By chapter 5 you're also going to run into Curl and all the rest of the Linux fun stuff. That might be great if that's what you're doing, but some of use the far superior VS 2017 tooling and Win 10, and the instructions just don't cut it. Why CouchDB was chosen instead of the far more common MongoDB is another major question (because Wilson likes it?) I'd like an answer for but have no expectation of getting.
Wilson could have chosen an approach that would be guaranteed to work with minimal problems on anyone's system. He didn't. Just because he found it to work fine doesn't mean everyone else will - and like I said above, I had started with a very clean CentOS VM and was installing things when I had to get expert help to overcome the brain-dead node-gyp way of doing native modules (if I didn't care for Oracle's tired java based installations of the normal kind before, it got 10x worse with Node).
If you love Linux more than you like software, the configuration work you'll do to use native libraries isn't going to be a bad problem, but expect to have to dig deep into many hidden areas to very selectively remove failed installs (but not everything), modify config files of various kinds, and re-do installations multiple times. Things WILL take, but it will not be by the book the way it's supposed to be. For those of us who aren't system admins but more into design, code, test and document, books like this are simply a mistake. Like the Security+ test will force you to realize, many places enforce separation of duties so it's not so simple for developers to get that additional system admin experience (fixing failures) that WOULD make this book more practical.
While the logic of how Wilson builds chapter upon chapter is good, and the section by section approach is well thought out, the potential issues regarding installations that just never turn out to be so simple. In Windows it's going to be very specific C++ and python and Windows SDK and visual studio versions and path and environment variables - which vary by what is the current version. If you are doing "normal" visual studio work you'll never see any of this - just install. Start working with node - easy as well. Install node. As soon as you run into a native module, all heck breaks loose and you will be on your own to troubleshoot it. If you set up a development environment on one system, doing it on a second 6 months later when an update or service pack uses slightly different libraries will screw up the node-gyp and native module use. It won't bother you for mainstream Visual Studio work at all. Wilson's book suddenly becomes a paperweight.
This book suffers the problems I can remember with some Java libraries years ago. Want to pick up Struts? Or maybe add a database object mapping? Well, everybook suddenly starts out with not the subject line but "I'm so smart I use these other 10 libraries all the time so I'm going to mix them in as I teach you about xxx and you won't know which code comes from which library" and so books that don't stick to the topic aren't very useful. I suppose I can put up with handlebars or something, but all kinds of tutuorials I've seen from You Tube to books like WIlson suddenly switch gears and get off the node track and into 3rd party issues. That only complicates the learning curve. I have come across some better written books that simply add some optional sections to chapters that use additional libraries, but by the next chapter are back to the more minimal configuration. If Wilson had stuck with the subject line the book would be much better. As I've flipped through the book several times, many pages do stick with node- but then I see those 3rd party references in selected places and realize "he's going to stick in these other things that aren't node and it won't be obvious what the code parts related to node really are - where they are and what they do". That's never a good approach.
Stick with the subject - that's a non-negotiable strategy for a how-to book. This book fails on that and I'm not giving it more than one star because I couldn't complete half of it and I have a clean installation that works great for other MEAN stack work.
If you can successfully get node-gyp built and install packages that depend on it and python, whether windows/mac/linux, FINE - you will probably find the book rather useful. If you can't, it will be very frustrating as you bought the book for a reason and that reason will be frustratingly difficult to achieve. If you don't know how to be sure you've got node-gyp built, and native module installs are working fine, don't hand over your money until you do.
I hope the author can revise this book with right version of nodejs and external package.