title: Why is rails not fully supporting writing evented code out out the box
body: <p>After Node.js came out, it was the one thing that popularized evented programming.
  But, Ruby does have EventMachine which supports writing evented code. </p>
  
  <p>The requirements for supporting eventing in rails are:<br>
  1. Evented server (thin, rainbows) which runs a reactor<br>
  2. Fibers (Ruby 1.9.3)  in order to make writing evented code easier, else we could have used threads.<br>
  3. All gems evented (example mysql2).  </p>
  
  <p>Nodejs showed the obvious benefits of evented programming. So why is the rails community NOT adopting eventmachine? I think one of the reasons rails is not fully portable to eventmachine is because of the dependency on underlying gems which may not be evented. But does anyone know if there is a plan to make a move in that direction?  </p>
  
  <p>Rails can do what Nodejs does, but Nodejs started out by advocating evented programming on all the library makers, so by convention most dependencies that you add to package.json in node, you know that it will be evented and will work with nodejs out of the box.</p>