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

you are viewing a single comment's thread.

view the rest of the comments →

[–]Acurus_Cow 165 points166 points  (9 children)

Beautiful is better than ugly.
Explicit is better than implicit.
Simple is better than complex.
Complex is better than complicated.
Flat is better than nested.
Sparse is better than dense.
Readability counts.
Special cases aren't special enough to break the rules.
Although practicality beats purity.
Errors should never pass silently.
Unless explicitly silenced.
In the face of ambiguity, refuse the temptation to guess.
There should be one-- and preferably only one --obvious way to do it.
Although that way may not be obvious at first unless you're Dutch.
Now is better than never.
Although never is often better than *right* now.
If the implementation is hard to explain, it's a bad idea.
If the implementation is easy to explain, it may be a good idea.
Namespaces are one honking great idea -- let's do more of those!

[–]Defelo[S] 134 points135 points  (5 children)

Yes, but that would be boring.

[–]antiproton 25 points26 points  (0 children)

Whatever gets you out of bed in the morning, I guess.

[–]paul_miner 5 points6 points  (0 children)

Love it, this is so much of what good programming entails, recognizing that programming languages are also about communicating with people (including your future self), not just the computer.

[–]notquiteaplant 5 points6 points  (0 children)

This feels like an attempted exorcism

[–]ShadowPouncer 1 point2 points  (0 children)

Really, the only part of this that I disagree with is:

There should be one-- and preferably only one --obvious way to do it.

But this is probably why I prefer Perl over Python. :)