On Tue, Jul 12, 2011 at 11:06 PM, Jeremy Dunck <jdu...@gmail.com> wrote: > 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.
Sounds like the interpreter is guarding global mutable state that is mutated during ordinary program execution (and not just during application bootstrap when the equivalents of defs and defns are run to populate namespaces). Perhaps a deeper redesign is in order? -- Protege: What is this seething mass of parentheses?! Master: Your father's Lisp REPL. This is the language of a true hacker. Not as clumsy or random as C++; a language for a more civilized age. -- 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
