-
-
Replying to @henrikfeldt
@henrikfeldt@avnerner lol you realize single-threaded async I/O predates threads by a deade, right? Your analogy is backwards1 reply 0 retweets 0 likes -
Replying to @henrikfeldt
@henrikfeldt@avnerner you realize I'm the author of a concurrent object oriented programming framework that makes that easy, right?1 reply 0 retweets 0 likes -
Replying to @bascule1 reply 0 retweets 0 likes
-
Replying to @henrikfeldt
@henrikfeldt@avnerner http://celluloid.io (and yes, it does async too)1 reply 0 retweets 0 likes -
Replying to @henrikfeldt
@henrikfeldt@avnerner each actor is backed by a native thread, yes. Each native thread consumes ~20kB of RAM in Ruby1 reply 0 retweets 0 likes
Replying to @henrikfeldt
@henrikfeldt @avnerner guess how many CPU cores each Node VM can use... yeah... it's 1
10:51 PM - 9 Sep 2012
1 reply
0 retweets
0 likes
-
-
Replying to @bascule0 replies 0 retweets 0 likesThanks. Twitter will use this to make your timeline better. UndoUndo
-
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.