Re: reduce()--what is it good for?
From: David C. Fox (davidcfox_at_post.harvard.edu)
Date: 11/10/03
- Next message: Alex Martelli: "Re: response time"
- Previous message: Alex Martelli: "Re: Am I the only one who would love these extentions? - Python 3.0 proposals (long)"
- In reply to: Alex Martelli: "Re: reduce()--what is it good for?"
- Next in thread: David C. Fox: "Re: reduce() anomaly?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Mon, 10 Nov 2003 20:12:43 GMT
Alex Martelli wrote:
>>P. S. I've seen a lot of talk about removing old features from Python,
>>or specifically old built-ins, because of bloat. Does this "bloat"
>>reduce performance, or does it refer to the extra burden on someone
>>learning the language or reading someone else's code?
>
>
> A slightly larger memory footprint, and larger built-ins dictionaries,
> can only reduce runtime performance very marginally. The "cognitive
> burden" of having built-ins that "don't carry their weight", on the
> other hand, is considered an issue *in Python*, because it doesn't fit
> in with Python's general philosophy and worldview. Python is meant to
> be a LEAN language (with a not-lean standard library of modules that
> are specifically imported when needed); certain "legacy" features are
> sub-optimal (and best removed, when the strict constraint of backwards
> compatibility can be relaxed) because they interfere with that (and
> built-ins are close enough to "the core language" that they _do_ need
> to be weighed severely in terms of "how often will they be useful").
Thanks, that's what I was trying to understand.
David
- Next message: Alex Martelli: "Re: response time"
- Previous message: Alex Martelli: "Re: Am I the only one who would love these extentions? - Python 3.0 proposals (long)"
- In reply to: Alex Martelli: "Re: reduce()--what is it good for?"
- Next in thread: David C. Fox: "Re: reduce() anomaly?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|