3 ms·
I get the feeling that what Node helps with is concurrency, although being fairly fast helps too. Ruby on Rails does not really have a good concurrency story f
by davidw 13y ago
I get the feeling that what Node helps with is concurrency, although being fairly fast helps too.
Ruby on Rails does not really have a good concurrency story for something like web sockets.
Although Rails is still what I would use for bootstrapping something where you're trying to find product/market fit and you are not absolutely sure that you need to squeeze out lots of performance from the get-go. Even if I knew I needed web sockets, I'd probably farm those out to a specific server to handle just those, most likely in Erlang.
- antirez 13y agoThat's a good point, but there was nothing in Javascript that was exceptionally better at event driven programming compared to other languages: probably the reverse actually, because of the lack of constructs to carry state.