2 ms·
> just as everyone "rallies" around EventMachine in Ruby. You can't really compare things this way. Very few people even use EventMachine, as it has significan
by steveklabnik 10y ago
> just as everyone "rallies" around EventMachine in Ruby.
You can't really compare things this way. Very few people even use EventMachine, as it has significant issues.
You can't just show that rotor and tokio are two different libraries; you've claimed that there's significant ecosystem fragementation. That's a very different claim. The same goes for the other three sets of links below: that you can find a bunch of GitHub repositories does not mean that there's actual fragmentation. Writing a memcached or Redis client is a good way to learn a language, even: I've known two people who independently did so for memcached + Rust, tossed them up on github, and that's it. (one of those is one of the links you've provided above, even.)
> Oh wow, a great redis library - objectively the most popular. Completely incompatible with all of the above AIO implementations.
Because it's synchronous. Once tokio has an actual 0.1 release of the full stack, which is to happen any day now, you'll see more consolidation.
> until a single solution is blessed by the Rust team.
Two of three of tokio's core team members are Rust core team members. We had a full talk on it at RustConf, and it was mentioned in the keynote. Mozilla has sponsored development of it in places.