What Is Node? eBook Brett McLaughlin
Download As PDF : What Is Node? eBook Brett McLaughlin 
Node.js. It’s the latest in a long line of “Are you cool enough to use me?” programming languages, APIs, and toolkits. In that sense, it lands squarely in the tradition of Rails,and Ajax, and Hadoop, and even to some degree iPhone programming and HTML5.
Dig a little deeper, and you’ll hear that Node.js (or, as it’s more briefly called by many,simply “Node”) is a server-side solution for JavaScript, and in particular, for receiving and responding to HTTP requests. If that doesn’t completely boggle your mind, by the time the conversation heats up with discussion of ports, sockets, and threads, you’ll tend to glaze over. Is this really JavaScript? In fact, why in the world would anyone want to run JavaScript outside of a browser, let alone the server?
The good news is that you’re hearing (and thinking) about the right things. Node really is concerned with network programming and server-side request/response processing.The bad news is that like Rails, Ajax, and Hadoop before it, there’s precious little clear information available. There will be, in time — as there now is for these other “cool”frameworks that have matured — but why wait for a book or tutorial when you might be able to use Node today, and dramatically improve the maintainability.
What Is Node? eBook Brett McLaughlin
We learned to use Node at Galvanize coding bootcamp. One day I asked our instructor why we were using Node instead of Apache. He didn't have an answer. If you spend one hour reading this book you'll learn the answer (Apache was made back when the web was big events such as assembling a dynamic webpage from a database or submitting a long form; now the web has more, smaller pieces requesting and sending small bits of data more often, so Node was made for handling micro-events quickly). You'll also learn the four parts of a Node server (the interactions, installed with require; creating the server with createServer; functions for handling requests; and specifying the port with listen). You'll also learn any you shouldn't use eval(), specifically, and, generally, why using different languages on the front and back ends leads to trouble as web apps become complex. You'll learn lots of stuff that our instructor should have told us.Product details
|
Tags : Amazon.com: What Is Node? eBook: Brett McLaughlin: Kindle Store,ebook,Brett McLaughlin,What Is Node?,O'Reilly Media
People also read other books :
- Euthyphro Plato Plato 9781466269415 Books
- MTEL 47 Math Middle School Math MTEL Preparation Mary DeSouza 9781461078449 Books
- Peace of Mind and Body 27 Days of Journaling to Health Happiness edition by Mari L McCarthy SelfHelp eBooks
- Vida Americana Portuguese Edition eBook Pedro A L Costa
- The Idiot Fyodor Dostoyevsky 9781536949827 Books
What Is Node? eBook Brett McLaughlin Reviews
This is a good place to start if you are trying to figure out the menagerie of JavaScript things, which appears to be popular now.
It literally just answers the question "What is Node?" It's a very short intro as to what NodeJS is and what it's for, but does not dig very deep into the "why". It's helpful if your management wants to know when to use Node vs, say, PHP or .NET, but only on a superficial level.
This book offers a decent primer on Node.js theory and suggests how Node might play a part in the ongoing paradigm shift toward a more responsive, interactive front-end web sites. If you're looking for a "how to write Node.js code" book, this is not it, but if you want a quick read on an emerging web technology and how you might implement it, this book is worth a look. It's free and only takes about a hour to read, so why not?
I'm not fully sure if this text answers the question, but it implants the idea that we should consider how application need to behave, regarding server and client interaction.
It felt as if when we were just getting started it ended. Made me wonder if I had been reading a sample chapter of a larger book all along.
I gave it 4 stars because the images/figures for illustrating, do not provide function to zoom in or browse full screen. With all the various screen sizes and form factors, it does retract from the overall experience. I fought with the images... pinching, double tapping, tap and hold to no avail. I felt foolish for trying something that is pretty much expected and standard.
This is a great quick read, with a great dose of objectivity, of an important technology. The title's question is answered quite well!
There's a great explanation of the round-trip JSON problem plus converters (small events), and I liked the "medium-event" perspective regarding the web. At the same time, McLaughlin warns us about "inertia of familiarity" (aka functional fixedness), which is all too common in IT (probably because of the complexity of solutions and the effort involved in learning how to use the latest "hammer.") Not all web servers should be run with node.js (and not all forms should be submitted with ajax, etc.). If you visit the MEANJS web site, you won't get this perspective and you could be taking a huge risk.
We need more books with this kind of professional engineering perspective (strengths and weaknesses).
I'm in the process of getting up to speed on the plethora of Web-related tools and technologies after YEARS of desktop application development. I've been reading up on several "hefty" technologies (e.g., ASP.NET MVC), and keep coming across small references to Node. I went in search of something that would give me an absolute "crash course" on Node so I could continue my heavier reading a little more informed and comfortable in my new landscape. "What Is Node" totally lived up to its reputation, delivering a quick but significant understanding of Node is only about 45 minutes (and that's WITH kids, lots of loud noises, and a glass of wine to bring the day to an end).
I wasn't looking for perfect or exhaustive. I was looking for the ability to understand where "Node.js" would fit in a conversation with colleagues, and "What Is Node" delivered.
While this book is not as bad as the other one-stars make it out to be, I'm giving it 1 because the information and arguments are obsolete. Node has established itself as the leading app server of its kind, and the theme of this booklet is to weigh the merits of Node against other programming styles. It's an irrelevant argument at this time, because a lot of development is being done on Node in this style of Javascript. There's no point in reading this book.
We learned to use Node at Galvanize coding bootcamp. One day I asked our instructor why we were using Node instead of Apache. He didn't have an answer. If you spend one hour reading this book you'll learn the answer (Apache was made back when the web was big events such as assembling a dynamic webpage from a database or submitting a long form; now the web has more, smaller pieces requesting and sending small bits of data more often, so Node was made for handling micro-events quickly). You'll also learn the four parts of a Node server (the interactions, installed with require; creating the server with createServer; functions for handling requests; and specifying the port with listen). You'll also learn any you shouldn't use eval(), specifically, and, generally, why using different languages on the front and back ends leads to trouble as web apps become complex. You'll learn lots of stuff that our instructor should have told us.
0 Response to "∎ Read What Is Node? eBook Brett McLaughlin"
Post a Comment