On Tue, Jul 12, 2011 at 9:47 PM, Ken Wesson <kwess...@gmail.com> wrote: ... > Python's major weakness, in this multicore age, is the global > interpreter lock -- has there been any progress on creating a viable > Python breed that has true concurrency?
FWIW, Jython and IronPython don't suffer from the GIL. CPython chooses to not penalize single-threaded performance in order to boost multi-threaded. The GIL-removal approaches tried so far have been based on finer-grained locks, which have single-threaded overhead. I think this makes sense given the maturity of the ecosystem and the single-threaded legacy. But PyPy doesn't have that constraint, and gives such good improvements over CPython that I think they'd be wise to abandon the single-threaded favoritism. -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en
