[Baypiggies] Frequently Argued Objections
charles.merriam at gmail.com
Fri Jun 20 06:40:40 CEST 2008
For "What's up with this global interpreter lock?" question:
A1. Much of Python is not multi-threaded. After many experiments,
variants, and systems, the unfortunate confusion is that removing the
global interpreter lock increases code complexity and reduces overall
reliability. For most systems, calling some subsystem that implements
threading, such as a database or transaction manager, is the correct
What's with "Duck Typing?":
A1. There are two key advantages over the Java style of strict
typing. First, many applications touch HTML, XML, or other networked
subsystems that pass around structured data in the form of text.
Using Duck typing greatly reduces the amount of code written for such
code, and removes the error prone type casting the occurs in other
languages. Second, there was a study (reference someone?) showing
that computer programmers with some experience did not, in practice,
make the typing mistakes prevented by strict typing.
On Thu, Jun 19, 2008 at 9:14 PM, Don Bennett <dpb at donbennett.org> wrote:
> One objection I've heard a few times, "What's up with this global
> interpreter lock?"
> It can come as a surprise to people trying to figure out why their
> multi-threaded programs aren't as fast as they expected.
> Shandy Brown wrote:
>> Hi all.
>> I'm trying to compile a list of frequent objections against using Python
>> and a rational response to each. Basically the same format as an FAQ.
>> It occurs to me that perhaps someone in the community has already come
>> up with such a list. So... any links?
>> Baypiggies mailing list
>> Baypiggies at python.org
>> To change your subscription options or unsubscribe:
> Baypiggies mailing list
> Baypiggies at python.org
> To change your subscription options or unsubscribe:
More information about the Baypiggies