Practical Node.js: Building Real-World Scalable Web Apps (Anglais) Broché – 11 juillet 2014
|Neuf à partir de||Occasion à partir de|
Les clients ayant acheté cet article ont également acheté
Descriptions du produit
Aucun appareil Kindle n'est requis. Téléchargez l'une des applis Kindle gratuites et commencez à lire les livres Kindle sur votre smartphone, tablette ou ordinateur.
Pour obtenir l'appli gratuite, saisissez votre adresse e-mail ou numéro de téléphone mobile.
Détails sur le produit
En savoir plus sur l'auteur
Dans ce livre(En savoir plus)
Quels sont les autres articles que les clients achètent après avoir regardé cet article?
Commentaires en ligne
Commentaires client les plus utiles sur Amazon.com (beta)
Author says: 'Figure 4-4 shows how the home page looks after adding style sheets'...Yes, maybe, but not until after adding menu.jade in includes, and after doing lots of additional changes in controller/model i.e. app.js (which is not done until two chapters later), and after you start 'mongod' process, and after you add some articles and... and counting.
The matter of the fact is that you cannot see the results of your .jade views without the model which in turn draws information from the persistence layer - but author doesn't find it worth mentioning. He simply states: 'Figure 4-4 shows how the home page looks after adding style sheets.' Isn't that just great? Regarding this, the approach to form the views first and then everything else is a bit strange - at least for a book. I've never seen it in my professional career.
This lone example illustrates the whole 'organization' of the book. Chaotic, unstructured with tons of pages wasted on listings of the code from the source file which is available anyway. Sometimes twice - as a listing and then 'full listing'. To make things worse, such listings are not accompanied by explanations, nuances, advices, best practices... he never draws readers attention to important details or pitfalls. Most of the time the author just says: 'The full code of xxxxx.xxx file is as follows', or for the variation's sake: 'Now we can look at the home page template index.jade that extends layout' which is nothing more but stating the obvious. Having said that, there are some useful advices when installing and setting up frameworks/libraries.
I also can't understand why author ruthlessly lists all the features of countless libraries he chooses to cover (why so many alternatives in the first place?). Most of the features he doesn't explain or, in a very rear occasion 'explains' in a wrong way. Take for instance the essential Node's module property: 'module.exports' and 'exports'. Instead of explaining the real difference (which is by the way very simple, but still important), he conveys disinformation: 'sometimes it's more fitting to invoke a constructor... In this case, module.exports is needed'. Unbelievable!
Author simply doesn't seem to fundamentally know the stuff he writes about, or he doesn't care.
The English language used is really basic and sometimes with the odd order of words in the sentence. This makes it hard for the author to explain the subtleties or transmit the essence. Try to compare it with the expressiveness of Ethan Brown or Michael S. Mikowski/Josh C. Powell who authored books on exactly the same subject. What a difference!
Don't get me wrong, I found easily every answer to my questions in the original documentation of each library/framework author covers, and within two days I deciphered the book - but was I supposed to?
Just for the sake of curiosity, I took a look at couple of other author's books. They all use the same almost-trivial projects which source codes author lists relentlessly all the way through.
My conclusion is that the author wrote couple of simple applications and then exploited every single line of code to contribute to the number of pages and number of books which he published under different names with different publishers (which still could have been okay if he analyzed the snippets properly).
The book is 'void'. Avoid void! (Douglas Crockford).
Why I love it:
1) Most chapters features an actual hands-on exercise to perform. Since I’m a kinesthetic learner, which means I learn by DOING, this is the key to making this book work for me. You can try to explain Node to me all you want, and I can take notes on theory, but I need actual written instructions in order to produce tangible results.
2) The book is organized flawlessly. Each chapter builds on the previous so I don’t have to go 0 to 60 without gaining momentum and confidence in a newish (to me) coding language.
3)The book walks you through how to create a few different projects, one of which I have used to jumpstart my own application development. This is probably the biggest benefit of all.
From setting up Node to understanding Mocha to error handling, Practical Node.js has become a fundamental resource in my arsenal.
For those who published 5 star reviews, have you ever read the book and followed the examples?