<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Node.js on Zach Alexander</title><link>https://zpalexander.com/tags/node.js/</link><description>Recent content in Node.js on Zach Alexander</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 20 Sep 2015 15:02:18 -0800</lastBuildDate><atom:link href="https://zpalexander.com/tags/node.js/index.xml" rel="self" type="application/rss+xml"/><item><title>JavaScript Promises With Node.js</title><link>https://zpalexander.com/posts/javascript-promises-with-nodejs/</link><pubDate>Sun, 20 Sep 2015 15:02:18 -0800</pubDate><guid>https://zpalexander.com/posts/javascript-promises-with-nodejs/</guid><description>&lt;p&gt;JavaScript is a non-blocking programming language, which means that one chunk of JS code will not necessarily wait for the lines above it to execute before beginning itself. In many cases this is a pretty awesome feature of the language. Imagine if your website was only able to run one window.onload call at a time. If your page needed to perform a number of calculations or data insertions in order to render correctly, things would take forever to load and users would see a bunch of unstyled content and blank boxes at the beginning of every page load. Yuck.&lt;/p&gt;</description></item></channel></rss>