Python's biggest compromises

Anthony_Barker anthony_barker at hotmail.com
Fri Aug 1 18:33:25 CEST 2003


> > What to you think python largest compromises are?
> > 
> > The three that come to my mind are significant whitespace, dynamic
> > typing, and that it is interpreted - not compiled. These three put
> > python under fire and cause some large projects to move off python or
> > relegate it to prototyping.
> 
> I don't view any of these as "compromises".  That word suggests that
> something was conceded, or that an intermediate position between two
> extremes was chosen to appease.  I don't think that either sense really
> applies to these features.
> 
> The three items that you listed are merely design choices.  While arguments
> over them are continuous, two of the design choices (interpreter, dynamic 
> typing) are consistent with Python's intended use as a language which 
> excels at rapid prototyping.  The third (white space) is merely a stylistic
> choice which is designed to encourage readable programs.  
> 
> "Compromises" in language design occur usually when a committee tries to 
> standardize a language, and each has differing views about how the language
> should be used.   While this occurs somewhat in Python, other languages
> have suffered more mightily from this particular disorder.  
> 	
> 	Mark

Excellent points - you are correct the ones I listed are design
choices.

Some people could be interpreted them as design "compromises". The
kind of people who would like to use the same tool for all problems.




More information about the Python-list mailing list