@rich0H @envygeeks @voidspace is Stackless multicore?
@rich0H @envygeeks @voidspace they're definitely more efficient. I'd challenge you to write something like Disruptor without one
-
-
@bascule@envygeeks@voidspace So that's a case where they're more efficient? Which part of "case by case" was hard? -
@rich0H@envygeeks@voidspace IMO VMs that can't utilize multiple cores natively are not long for this world, at least for serious apps -
@bascule@envygeeks@voidspace Your assumption that all the cores live on the same box isn't a longterm worldview either! -
@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 - 1 more reply
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.