Guido van Rossum wrote:
> I was pleasantly surprised to find a pointer to this article in a news
> digest that the ACM emails me regularly (ACM TechNews).
>
> http://gcn.com/vol1_no1/daily-updates/28026-1.html
>
> One thing that bugs me: the article says 3 or 4 times that Python is
> slow, each time with a refutation ("but it's so flexible", "but it's
> fast enough") but still, they sure seem to harp on the point. This is
> a PR issue that Python needs to fight -- any ideas?
In public documents - documentation, release notes, etc etc.:
Remove all references to the performance of Python. From now on, Python
has always been extremely fast, has no need to get any faster, and any
speed increases are of so little importance that they barely rate a
mention (no percentage increases mentioned in release notes).
If you must mention performance, do it in terms of the use of C modules
such as numarray, and for benchmarks that other languages cant compete
in. Write a benchmark which uses common C extensions, that Java cant
compete with.
Replace all references to a 'Python interpreter' with 'Python Virtual
Machine'
Ensure that the terms 'Python compiler' and 'compiled python' are
liberally sprinkled around. Start emphasising the compilation step from
python source to python bytecodes instead of making it transparent.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4