@alex_gaynor @bascule Sure, it's just another JVM lang…but we've worked through concurrency + Ruby issues for years now.
@voidspace *shrug* just the author of a multicore concurrency framework. I like the idea of Jython, but carry on...
-
-
@bascule@voidspace Jython and IronPython are really the only GIL free impl but you can always use threading (meh) or http://docs.python.org/dev/library/concurrent.futures.html … -
@envygeeks@bascule@voidspace Threading you're still bound by the GIL (Not a problem if you're hitting lots of C). Stackless is badass -
@rich0H@envygeeks@voidspace is Stackless multicore? -
@bascule@envygeeks@voidspace Evidently not, though personally I'd prefer mutliple stackless processes to one running JVM. (personal pref) -
@rich0H@envygeeks@voidspace yeah, that's what I thought. I like shared heaps FOR SPEED! -
@bascule@envygeeks@voidspace I prefer IPC like sendfile(2) over shared heaps. That's personal though, not "this is better than that". -
@rich0H@envygeeks@voidspace there's a lot more complexity and inefficiency with that kind of approach, but it has some merits -
@bascule@envygeeks@voidspace inefficiency? MMU dependant I guess. scales across machines transpaently, but both valid. Case by case imo. - 14 more replies
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.