News for hackers. Stuff that matters.
Re:Thoughts on Rails, Node, and the web apps of today by ef4 on Thursday July 12, 2012 @12:46PM (#4235407)
The problem with the "solve it with a library" answer is interoperability. You and your dependencies usually need to agree on which paradigm you're going to use.

The Node ecosystem clearly has no consensus on this point. So you spend a lot of time gluing pieces together.

And I do know how to find the style I'm after. At the moment I'm doing a lot with Q, and I have also used node-fibers. But in either case, you end up doing a lot of plumbing, because you end up depending on other people who chose different (or non-existent) high-level flow control abstractions.

Re:Thoughts on Rails, Node, and the web apps of today by pooriaazimi on Thursday July 12, 2012 @05:51PM (#4237062)
Care to share a link to Q? I haven't heard of it before, and as you might guess, it's almost impossible to find it through search :)

Edit: forget it. Someone else mentioned it in another comment: https://github.com/kriskowal/q/