Live data from Hacker News

"Ruby developers need to stop using EventMachine. It's the wrong direction."

slideshare.net

71–72 of 72 posts

Re: "Ruby developers need to stop using EventMachine. It's the wrong direction."

#71
post #58
post #47

Earlier quoted context omitted.

At least 2 years ago, twisted did not use libevent, it was mostly pure python except for a very tiny piece of code (and optional stuff of course). I am sure you could write a libevent-based reactor, but twisted was started a long time ago (10 years ? The twisted book in o'Reilly was published in 2005), before libevent existed I think.

No, libevent existed before Twisted; its first release was in 2000, and we used it extensively at Arbor Networks just a couple years later.

Thanks for the correction. Seems that I confused the dates with libev that came after.

Re: "Ruby developers need to stop using EventMachine. It's the wrong direction."

#72
post #52

There's a fork out there called EventMachine-LE, which is currently in active development for latest features (i.e. IPv6). https://github.com/ibc/EventMachine-LE Anyway, just wanted to throw it out there that I've deployed several production apps (gaming/messaging servers) using EventMachine, and combined with em-synchrony, I'm pretty comfortable with its performance and limitations. There seems to be good community…

Sidekiq is probably the best example of Celluloid in action.

Correct, and for those interested in approaching Celluloid, here is post that demonstrates a concurrent "Hello, world" program: http://danielsz.posterous.com/167870244
Post reply on HN