@henrikfeldt @avnerner you realize I'm the author of a concurrent object oriented programming framework that makes that easy, right?
-
-
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 the "quantum" of your process? as in the kernel's scheduler quantum? you realize CPUs have more than 1 core nowadays?1 reply 0 retweets 0 likes -
Replying to @bascule1 reply 0 retweets 0 likes
-
Replying to @henrikfeldt
@henrikfeldt@avnerner not sure what you're trying to compare to if not Node, but it does a ton of context switching: http://aphyr.com/posts/244-context-switches-and-serialization-in-node …1 reply 0 retweets 0 likes
@henrikfeldt @avnerner so, other systems that use native threads? Mmmkay... yeah I got one of those
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.