Over a million developers have joined DZone.

Why Python? (Sad Follow-up)

DZone's Guide to

Why Python? (Sad Follow-up)

Steven Lott reflects on an individual's reaction to a recent article.

· Web Dev Zone ·
Free Resource

Jumpstart your Angular applications with Indigo.Design, a unified platform for visual design, UX prototyping, code generation, and app development.

In "Why Python" I linked to a deep and sophisticated analysis of programming languages. Anyway, I thought it was a deep and sophisticated analysis...

I got a reply that shows how wrong I was. Here's the quote:

The point is that the Python ecosystem has a lot to offer. We could argue about the language design choices. However, why bother? Why not just take advantage of what the ecosystem has to offer.

Ah. Discussing the language is just "arguing." I guess the points are all debatable and my comparison of Python to any benchmark is just the seed for an argument. A religious war, perhaps. I guess this wasn't compelling. It was a Why bother?

Why bother pointing out the strong points of the language?

The email emphasized the "ecosystem" with a cool, but short example of how scipiy.spatial.KDTree works. 

It appears that—for some people—"Python code actually works" is a useful response to "Why Python?" 

I would have thought that "Python code actually works" was a precondition to even discussing the value proposition behind Python.

But—clearly—I was wrong. The mere fact of a working example is a Very Important Thing™.

What does this mean?

  1. There are people who use software that doesn't actually work. When they see software that works, it's important. Very important.
  2. When software actually works, these people find this simple fact to be a compelling and substantial argument for placing a high value on the software.
  3. Other considerations like clarity and simplicity aren't relevant. If these poor souls are suffering software that doesn't actually work, then broken and obscure is still broken. Other parts of the long discussion from Wirth are just arguing points.

The email included "consider amending the why python? blog w/ the other big pro: ecosystem"... I'm not sure I actually understand the request. When code that works is a "big pro," this comes from a world I can't pretend to understand.

Also. The example code used xrange(). Which is a Python 2 smell. Those days are passed.

Related Refcard:

Take a look at the Indigo.Design sample applications to learn more about how apps are created with design to code software.


Published at DZone with permission of

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}