4 ms·
Wrong. Wrong, and Wrong. Plenty of people - all over the world including myself - can use threads (and python threads) perfectly well understanding their limita
by jnoller 16y ago
Wrong. Wrong, and Wrong. Plenty of people - all over the world including myself - can use threads (and python threads) perfectly well understanding their limitations. It does benefit our applications just fine.
That said, this GIL drum does get old.
- tetha 16y agoIn my opinion, threads are in a similar vein like goto and eval. It is true, that a good, disciplined programmer with the goal of a performant application with simple and good code can use gotos in a way which enhances the code, and he can use threads to enhance the performance without bringing all living hell down on people around him. However, it is also true that a lot of people who only consider themself to be a good programmer want to use threads, gotos and all these powerful constructs, and because some dude called tetha said that good programmers can use them well, they will use them. But since they are not good programmers, a mess will happen. Thus, strongly advocating against threads -- while wrong -- is still right in my opinion. Granted, I don't want to go off-topic too much, but I cannot talk about the GIL too much, because the matter is too delicate and complicated for me. Sometimes the GIL enhances performance, sometimes it degrades it. Live with it, and if you really need parallelism, use the libraries out there for it.
- jnoller 16y agoI'm surprised; I find threads both conceptually simple, easy to explain and criminally easy to use - it's when you start talking about locks, semaphores/etc things sort of go sideways for most people.