-
-
@bascule@jondot@henrikfeldt "Need" is strong, I think that in some cases troubleshooting Threads is an issue you don't face with Node. -
@avnerner@jondot@henrikfeldt yeah, you just have to troubleshoot the callback that's not firing in the expected order (or at all) :P -
@bascule@avnerner@henrikfeldt node has its own cans of worms. Use what works, but be very suspicious of your node apps. CPS is illusive
End of conversation
New conversation -
-
-
-
@henrikfeldt@avnerner lol you realize single-threaded async I/O predates threads by a deade, right? Your analogy is backwards -
-
@henrikfeldt@avnerner you realize I'm the author of a concurrent object oriented programming framework that makes that easy, right? -
-
@henrikfeldt@avnerner http://celluloid.io (and yes, it does async too) -
-
@henrikfeldt@avnerner each actor is backed by a native thread, yes. Each native thread consumes ~20kB of RAM in Ruby - 6 more replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.