<story><title>Rubinius 2.0 released</title><url>http://rubini.us/2013/10/04/rubinius-2-0-released/</url></story><parent_chain><item><author>rahoulb</author><text>Genuine question: what advantage does Node give you over EventMachine?</text></item><item><author>1qaz2wsx3edc</author><text>&amp;gt; Concurrent and distributed applications aren&amp;#x27;t the future anymore, they are the present. They are vital to business success. The many talented developers that are passing over Ruby for Erlang, Go, Clojure and Node are draining Ruby of talent and vitality.&lt;p&gt;As someone who has been working with MRI since 2006-ish, I feel this statement is accurate. MRI is stagnating around the GIL. Rails last lost some of it&amp;#x27;s edge and this is in part responsible. Since about 2011, I&amp;#x27;ve invested into Erlang (elixir), and mostly NodeJS. They&amp;#x27;re truly communities that are evolving well, they are applying themselves well to new problems inherit to changes in application building demands.</text></item></parent_chain><comment><author>tomphoolery</author><text>One thing I enjoy about NodeJS is their standard library is asynchronous until you want it to be. Most of the NodeJS libs in NPM are also designed in this way. With EventMachine, you have to be careful what you&amp;#x27;re using because some of those RubyGems will probably include blocking IO.&lt;p&gt;When you&amp;#x27;re doing &lt;i&gt;that&lt;/i&gt; kind of programming, I think it&amp;#x27;s better to use a language or ecosystem designed specifically for that purpose rather than use a library such as Twisted or EventMachine which is inside another language that may or may not support what you&amp;#x27;re doing. This has no basis in theory or anything, just my own experience. Makes things easier for me, that&amp;#x27;s all.</text></comment>
<story><title>Rubinius 2.0 released</title><url>http://rubini.us/2013/10/04/rubinius-2-0-released/</url></story><parent_chain><item><author>rahoulb</author><text>Genuine question: what advantage does Node give you over EventMachine?</text></item><item><author>1qaz2wsx3edc</author><text>&amp;gt; Concurrent and distributed applications aren&amp;#x27;t the future anymore, they are the present. They are vital to business success. The many talented developers that are passing over Ruby for Erlang, Go, Clojure and Node are draining Ruby of talent and vitality.&lt;p&gt;As someone who has been working with MRI since 2006-ish, I feel this statement is accurate. MRI is stagnating around the GIL. Rails last lost some of it&amp;#x27;s edge and this is in part responsible. Since about 2011, I&amp;#x27;ve invested into Erlang (elixir), and mostly NodeJS. They&amp;#x27;re truly communities that are evolving well, they are applying themselves well to new problems inherit to changes in application building demands.</text></item></parent_chain><comment><author>sturadnidge</author><text>The creator of Node was something of a Rubyist, i believe the main reason was around the stdlib &amp;#x2F; ecosystem not being event oriented, making it difficult to build non-blocking applications. EventMachine may well have strategies to defeat this, I just don&amp;#x27;t know.&lt;p&gt;This video gives some good insight into what led to his decision to start fresh rather than try and change things in Ruby &lt;a href=&quot;http://m.youtube.com/watch?v=SAc0vQCC6UQ&quot; rel=&quot;nofollow&quot;&gt;http:&amp;#x2F;&amp;#x2F;m.youtube.com&amp;#x2F;watch?v=SAc0vQCC6UQ&lt;/a&gt;&lt;p&gt;So that&amp;#x27;s probably the biggest thing about Node - everything in the core is built with event orientation in mind, so you know you&amp;#x27;re not going to hit something that will block and kill you, and that minset is pervasive in userland too.</text></comment>