3 ms·
You can deal with the GIL, it's not the death sentance some people think it is, I agree. But this guy actually DOES try to argue it's a _positive_ somehow! He
by jrochkind1 12y ago
You can deal with the GIL, it's not the death sentance some people think it is, I agree.
But this guy actually DOES try to argue it's a _positive_ somehow! He really is claiming it's all unicorns and rainbows, he doesn't mention _any_ negative to it, he says it doesn't effect concurrency at all, look at generators and deferreds that proves it (not true, a misdirection), he even tries to say it's a positive, the "GIL is a performance optimization for most use cases of Python, and a development ease optimization for virtually all CPython code. The GIL makes it much easier to use OS threads"
I think either this is an intellectually dishonest argument meant to confuse less-technical people, or the guy doesn't understand what he's talking about.
And I still think python is probably fine for 'enterprise', although as always it depends on what you're doing with it!
- dragonwriter 12y agoThe GIL absolutely makes it easier to use OS threads in terms of development ease, but the "performance optimization" piece I can't really see, except insofar as the development ease aspect means that developers are less likely to avoid using threads where they would provide a performance benefit.
- slantedview 12y ago"The GIL absolutely makes it easier to use OS threads in terms of development ease" Yes, but pretending that you can have the ease of not worrying about thread safety while still having the performance benefits of multi-threading (real OS threads, mind you) is ridiculous. You can't have your cake and eat it too.
- dragonwriter 12y agoYou can have the ease with some of the performance benefits with the GIL (since the GIL is released in certain low level operations) -- because, for the things where you get the performance benefits, someone else has dealt with the pain of not having the ease.
- gdwatson 12y agoI think the performance comment is in regard to the single-threaded common case. The reason the GIL is still around is that Guido has said that a replacement is only acceptable if it avoids performance regressions for single-threaded code. Most of the Python world seems to have concluded that that's not possible in practice.