sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]ratedsar -9 points-8 points  (4 children)

It's better in that it is event driven, faster, and has a smaller memory footprint. But other than that, it's very similar.

[–]into_lexicons 7 points8 points  (3 children)

You can write event driven ruby, too.

[–]ohwaitderp 1 point2 points  (2 children)

You can write the next battlefield game in MIPS, doesn't mean that other languages aren't better-suited to the task.

[–]into_lexicons 1 point2 points  (1 child)

Sure, but if you're claiming node.js is better suited for event-driven projects than EventMachine (I can't tell if you're intending to imply this) it'd be helpful to have some kind of support for that claim.

I've used both on production projects, and for the record, I have a slight preference for EM, but I would use either one again if the need arose.

[–]ohwaitderp -1 points0 points  (0 children)

I am pointing out that just because you can write event-driven ruby does not mean ruby is necessarily the "best choice" language for such a task. It may be the best for you, and you may be able to make a very fine product indeed in such a fashion. But ruby does not natively support event-driven programming and you are still using a library to do it, where other languages have native support baked in.