<story><title>Node v4.0.0</title><url>https://nodejs.org/en/blog/release/v4.0.0/</url></story><parent_chain><item><author>blowski</author><text>As somebody who uses Node only at the periphery of my role (for things like the Zombie browser, and SASS parsing) the massive instability has put me off from relying on it for anything core.&lt;p&gt;Documentation is quickly out of date, libraries seem to have incompatibilities which only become obvious when they don&amp;#x27;t work, there&amp;#x27;s no &amp;#x27;recommended&amp;#x27; approach for even basic tasks.&lt;p&gt;I won&amp;#x27;t pretend I&amp;#x27;m speaking for everyone, as clearly there are lots of people doing great things with Node. However, it doesn&amp;#x27;t seem to be a language like Ruby or Python where I would feel comfortable using it for a small but important project.&lt;p&gt;I&amp;#x27;m always grateful to everyone who works on open source projects, but I wouldn&amp;#x27;t hold Node up as a great example of the open source community.</text></item><item><author>dcwca</author><text>The io.js fork and subsequent merge back into Node.js, including the birth of the Node Foundation, has been one of the best examples of the power of open source I have ever seen in action.&lt;p&gt;The situation went from bad, to worse, to the best possible outcome, and that&amp;#x27;s remarkable to say the least.&lt;p&gt;Congratulations to everyone involved and thank you for the hard work.</text></item></parent_chain><comment><author>dcwca</author><text>Instability is the very thing this merge and the foundation seek to address. Where there was once an uncertain future, there is now a Board of Directors and a Technical Steering Committee bound by a Open Governance Model.&lt;p&gt;The future has never looked more stable for Node, just take a peek at the names of the companies sitting on the board: &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;nodejs.org&amp;#x2F;en&amp;#x2F;blog&amp;#x2F;announcements&amp;#x2F;foundation-elects-board&amp;#x2F;&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;nodejs.org&amp;#x2F;en&amp;#x2F;blog&amp;#x2F;announcements&amp;#x2F;foundation-elects-b...&lt;/a&gt;</text></comment>
<story><title>Node v4.0.0</title><url>https://nodejs.org/en/blog/release/v4.0.0/</url></story><parent_chain><item><author>blowski</author><text>As somebody who uses Node only at the periphery of my role (for things like the Zombie browser, and SASS parsing) the massive instability has put me off from relying on it for anything core.&lt;p&gt;Documentation is quickly out of date, libraries seem to have incompatibilities which only become obvious when they don&amp;#x27;t work, there&amp;#x27;s no &amp;#x27;recommended&amp;#x27; approach for even basic tasks.&lt;p&gt;I won&amp;#x27;t pretend I&amp;#x27;m speaking for everyone, as clearly there are lots of people doing great things with Node. However, it doesn&amp;#x27;t seem to be a language like Ruby or Python where I would feel comfortable using it for a small but important project.&lt;p&gt;I&amp;#x27;m always grateful to everyone who works on open source projects, but I wouldn&amp;#x27;t hold Node up as a great example of the open source community.</text></item><item><author>dcwca</author><text>The io.js fork and subsequent merge back into Node.js, including the birth of the Node Foundation, has been one of the best examples of the power of open source I have ever seen in action.&lt;p&gt;The situation went from bad, to worse, to the best possible outcome, and that&amp;#x27;s remarkable to say the least.&lt;p&gt;Congratulations to everyone involved and thank you for the hard work.</text></item></parent_chain><comment><author>untog</author><text>I mean, Ruby was created in 1995, Python in 1991. Node was first released in 2009. That&amp;#x27;s not an entirely fair comparison since, of course, &lt;i&gt;JavaScript&lt;/i&gt; was created long before Node, but Node introduced the language to a new environment, and a lot of complications needed (and in some cases, still need) to be sorted out.&lt;p&gt;As for no recommend approach - that&amp;#x27;s deliberate. I don&amp;#x27;t think most people working on Node &lt;i&gt;want&lt;/i&gt; a Rails equivalent.</text></comment>