Pattern of memory&execution isolation is well established yet it's constantly reimplemented instead of adopting it as a scalable primitive.
@stevedekorte if you’re talking about what I think you’re talking about, actors + ownership transfer is the solution ;)
-
-
@bascule I'm suggesting OSs efficient support tiny processes just as some file systems efficient support tiny files. -
@stevedekorte ucontext? or fibers on windows… -
@bascule That doesn't scale across cores and assumes a monolithic userland model. -
@stevedekorte yeah, you have to write an Erlang or Go-like scheduler (I wrote something similar for Celluloid that uses threads+coroutines)
End of conversation
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.