@rich0H @envygeeks @voidspace there's a lot more complexity and inefficiency with that kind of approach, but it has some merits
@rich0H @envygeeks @voidspace o_O umm here's one of my projects: https://github.com/celluloid/dcell
-
-
@bascule@envygeeks@voidspace At which point it's no longer a shared heap. I'm not saying either is better. Absolutes are short sighted. -
@rich0H@envygeeks@voidspace when you're on a multicore machine with a NUMA-like architecture, a shared heap makes the most sense -
@bascule@envygeeks@voidspace Always. For all usecases. Definitely. -
@rich0H@envygeeks@voidspace for managed language runtimes, yeah, pretty much -
@bascule@envygeeks@voidspace Except this discussion was managed runtime vs multiprocess and IPC.
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.