What Is Node?

Nonfiction, Computers, Programming, Programming Languages, CGI, JavaScript, Perl, VBScript, Internet, Web Development
Cover of the book What Is Node? by Brett McLaughlin, O'Reilly Media
View on Amazon View on AbeBooks View on Kobo View on B.Depository View on eBay View on Walmart
Author: Brett McLaughlin ISBN: 9781449314484
Publisher: O'Reilly Media Publication: July 13, 2011
Imprint: O'Reilly Media Language: English
Author: Brett McLaughlin
ISBN: 9781449314484
Publisher: O'Reilly Media
Publication: July 13, 2011
Imprint: O'Reilly Media
Language: English

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.

View on Amazon View on AbeBooks View on Kobo View on B.Depository View on eBay View on Walmart

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.

More books from O'Reilly Media

Cover of the book Using SVG with CSS3 and HTML5 by Brett McLaughlin
Cover of the book Beyond Blame by Brett McLaughlin
Cover of the book Security for Web Developers by Brett McLaughlin
Cover of the book High Performance Linux Clusters with OSCAR, Rocks, OpenMosix, and MPI by Brett McLaughlin
Cover of the book Subject To Change: Creating Great Products & Services for an Uncertain World by Brett McLaughlin
Cover of the book The Evolution of Data Products by Brett McLaughlin
Cover of the book Elegant SciPy by Brett McLaughlin
Cover of the book Open Sources by Brett McLaughlin
Cover of the book iOS Sensor Apps with Arduino by Brett McLaughlin
Cover of the book High Performance Spark by Brett McLaughlin
Cover of the book 20 Recipes for Programming MVC 3 by Brett McLaughlin
Cover of the book Designing Connected Products by Brett McLaughlin
Cover of the book Designing for Performance by Brett McLaughlin
Cover of the book 97 Things Every Software Architect Should Know by Brett McLaughlin
Cover of the book Head First Programming by Brett McLaughlin
We use our own "cookies" and third party cookies to improve services and to see statistical information. By using this website, you agree to our Privacy Policy