News for hackers. Stuff that matters.
Re:Node.js - A giant step backwards? by peterhunt on Wednesday January 25, 2012 @02:20PM (#3511235)
Deferreds make your code nicer, but they still don't magically make your code composable.

What would make Node more attractive is if it supported copy-on-write multithreading and gave me a way to cheat and use asynchronous I/O (like a wait(myFunctionThatTakesACallbackOrDeferred) function)

Re:Node.js - A giant step backwards? by bascule on Wednesday January 25, 2012 @02:24PM (#3511254)
There are many ways to compose deferrables, primarily by grouping several of them together into something which is also a deferrable. See the em-scenario gem for examples:

https://github.com/athoune/em-scenario

Note: I still think this approach sucks.

V8 provides a really awesome shared-nothing multithreading scheme via web workers. It's just nobody uses them.

Re:Node.js - A giant step backwards? by peterhunt on Wednesday January 25, 2012 @02:29PM (#3511285)
Oh right that's definitely true and is much more elegant. I was talking about when a function written in synchronous style (in a long stack of synchronous calls) needs to call something asynchronous.
Re:Node.js - A giant step backwards? by ufo on Wednesday January 25, 2012 @04:26PM (#3511810)
I wouldn't say the problem with Deferreds is composability - the big problem, as you already mentioned, is fragility towards future changes