Re:How LinkedIn used Node.js and HTML5 to build a better, fa...
by cpher on Tuesday August 16, 2011 @11:19AM
(#2891477)
Great explanation--the light bulb finally went on for me regarding node.js.
Regarding the other framework event models (esp. EventMachine), is it beneficial or wise to use node for the I/O intensive stuff and another framework (e.g. rails) for the rest? Or does it make more sense to stay in the Ruby world? I'm sure there are lots of caveats to this question but it would be nice to see how node.js can integrate with existing web frameworks rather than trying to build everything with node.
[ Parent
| on HN ]
Re:How LinkedIn used Node.js and HTML5 to build a better, fa...
by pchristensen on Tuesday August 16, 2011 @12:43PM
(#2891843)
I've had this question myself - how much of the benefit of Node is because of Node, how much is because of JS/V8, and how much is because of evented programming generally?
For instance, if you switch from Rails to EventMachine, will you get most of the benefits of Node, or will you still be bogged down by Ruby's speed and resource consumption?
Re:How LinkedIn used Node.js and HTML5 to build a better, fa...
by akavlie on Tuesday August 16, 2011 @05:28PM
(#2892966)
A lot of it is thanks to V8 I think.
But an issue commonly raised with EventMachine (and gevent etc. on Python) is that many common libraries contain blocking code that you cant get rid of, whereas Node modules have all been programmed to avoid blocking at all costs.
Re:How LinkedIn used Node.js and HTML5 to build a better, fa...
by colin_jack on Tuesday August 16, 2011 @04:42PM
(#2892803)
I've not seen anyone do a proper investigation, I definitely think it would be interesting.