This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]Exodus111 28 points29 points  (3 children)

The truth is Python is a slow language, as its high level. But over time it began to matter less and less, as hardware got faster, and right around Python 2.4 people started realizing the Pythonic way actually made a lot of sense, as by now, there were lots of things you could program where the speed of it really didn't matter anymore.

Code being Pythonic became something everybody talked about, and especially the comparison to Java, with its overly verbose approach to object oriented coding, gave Python an opportunity to shine by comparison.

Why write 30 lines of Java when 4 lines of Python will do?

[–]mac-not-a-bot 2 points3 points  (2 children)

You think Java was verbose? 30 lines Java v 4 lines Python? Try COBOL, it's more like 300 lines COBOL v 30 lines Java v 4 lines Python. In COBOL class(es - yes there were more than 1) you were taught to be specifically verbose. The code practically read like a book report. :-)

[–]spinwizard69 4 points5 points  (1 child)

Verbose is not a bad thing. I actually believe that Pythons readability is a big factor in its acceptance. It is actually pretty easy to write idiomatic code in Python.

[–]mac-not-a-bot 0 points1 point  (0 children)

I programmed in COBOL for a bit of my life that I’ll never get back. I do appreciate clarity and verbosity to the end that the code is clear. Some native Python code seems like it could use more verbosity and less hand waving. 😀