3 ms·
As I perhaps somewhat self-aggrandizingly consider myself one of the most knowledgable people regarding I/O in the Ruby world, I decided to peek around the Star
by defunkt 18y ago
As I perhaps somewhat self-aggrandizingly consider myself one of the most knowledgable people regarding I/O in the Ruby world, I decided to peek around the Starling source and see what I discovered. What I found was a half-assed and pathetically underperforming reinvention of EventMachine, an event-based networking framework for Ruby which is the Ruby answer to the Twisted framework from Python.
The non-evented Starling was multi-threaded and used a thread pool to manage connections. I'm unclear on how that is a 'half-assed implementation of EventMachine' and not simply a multi-threaded network daemon.
- tptacek 18y agoEventMachine supports an actor-style threading model, which may be what Tony was comparing it to; pretty clearly, Tony Arcieri knows EventMachine and async programming --- he's one of the better known people in the EventMachine "community".
- deleted 18y ago[deleted]
- defunkt 18y agoDoes that make every multi-threaded network daemon that manages a thread pool of connections a 'half-assed implementation of EventMachine' then? (I know who Tony is. I co-wrote Evented Starling.)
- tptacek 18y agoOk. It wasn't clear from your comment whether you were saying Arcieri didn't know what he was talking about. Sorry.