On Tue, 03 Mar 2009 10:11:10 PST "Roman V. Shaposhnik" <r...@sun.com> wrote:
> On Tue, 2009-03-03 at 07:19 -0800, David Leimbach wrote:
>
> > My knowledge on this subject is about 8 or 9 years old, so check with your
> local Python guru....
> >
> >
> > The last I'd heard about Python's threading is that it was cooperative
> > only, and that you couldn't get real parallelism out of it. It serves
> > as a means to organize your program in a concurrent manner.
> >
> >
> > In other words no two threads run at the same time in Python, even if
> > you're on a multi-core system, due to something they call a "Global
> > Interpreter Lock".
>
> I believe GIL is as present in Python nowadays as ever. On a related
> note: does anybody know any sane interpreted languages with a decent
> threading model to go along? Stackless python is the only thing that
> I'm familiar with in that department.
Depend on what you mean by "sane interpreted language with a
decent threading model" and what you want to do with it but
check out www.clojure.org. Then there is Erlang. Its
wikipedia entry has this to say:
Although Erlang was designed to fill a niche and has
remained an obscure language for most of its existence,
it is experiencing a rapid increase in popularity due to
increased demand for concurrent services, inferior models
of concurrency in most mainstream programming languages,
and its substantial libraries and documentation.[7][8]
Well-known applications include Amazon SimpleDB,[9]
Yahoo! Delicious,[10] and the Facebook Chat system.[11]
