celluloid-io

https://github.com/tarcieri/celluloid-io --> 404 maybe it's a good point why I cannot upvote it

When I made this comment the other day, I wasn't actually serious that someone should build a JavaScript compiler that does CPS: "CPS is also generally used as an IR in compilers, not something you write by hand" http://news.ycombinator.com/item?id=3511211 This reminds me of my Celluloid::IO system in Ruby (which uses coroutines to provide a synchronous API), except Celluloid::IO lets you have as many event loops as you want: https://github.com/tarcieri/celluloid-io

em-synchrony's problem is it has people wrap asynchronous libraries one-at-a-time. There's a few problems with that: You're exposing a synchronous API, but still can't take advantage of the huge ecosystem of Ruby libraries that already expose synchronous APIs. Wrapping libraries becomes a one-off chore. Each individual library must be wrapped to work in an em-synchrony system, and if the libraries aren't both asynchronous and wrapped in fibers you can't use them. This not only shrinks the ecosystem of libraries further, but is also more error-prone than providing a general coroutine abstraction around socket IO. Providing a generalized abstraction for doing synchronous I/O with sockets/fibers and an evented backend is exactly what I'm working on in Celluloid::IO: https://github.com/tarcieri/celluloid-io

There are ways to compose functions, like the deferrable pattern. They just all kind of suck and are poor replacements for having a stack. I'm all for using coroutines to solve this problem. That's the approach taken by my Celluloid::IO library: https://github.com/tarcieri/celluloid-io Unfortunately Ryan Dahl is adamantly opposed to coroutines so that's not going to happen in Node any time soon.