A number of people commented on the article in GCN that talks about the new Python 2.4 release, and wondered if more could not be done to address the perception of speed. The point is made that although people mention all of the benefits of Python, like ease of use, flexibility, they always come back to making references to its speed. And the question is raised, “what can we do to counter this perception?”. I think the answer lies in a quote by a user in that same article: “At first, Doak was worried a Python-based program would not run simulations quickly enough, however he found performance to be acceptable”.
Let’s turn this around. Forget about trying to create a perception that Python is fast. Compiled languages will always be faster, at least for large applications. Or at least they’ll be perceived that way. So let’s acknowledge that upfront, but say “Python is fast enough for most uses”, but then go on to say “and in addition to its acceptable speed, it offers many advantages like elegance, ease-of-use, flexibility, easy code maintenance (since the code is still understandable 6 months later!) etc.
Marketers of other products have used this same technique successfully. For example, at one time there was a perception that Kellogg’s Corn Flakes were old and boring. Sales were slipping. Rather than refute that, marketers turned the issue on its head by emphasizing that the product had been around a long time because it was good, and good for you. Hence was born the slogan “taste them again, for the first time”. And sales of the product turned around.
Possible slogan for Python: “Fast enough, and better in many ways”.
