Monday, January 30, 2012

Python is haaaard.

Well, not really.

[ Python ] is a language I decided I'd sit down and learn for a project I've taken upon myself to write.

So far I'm two mostly-working modules in and it's not terribly difficult to understand what I'm doing.

A relevant citation is what python returns when the user types import this:

The Zen of Python, by Tim Peters

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!

I've tried to keep what I'm doing to be just that: easy to explain and read and understand. I have not, however, made it easy to write or optimize (mainly because I'm not the most competent programmer out there).

The language encourages ease-of-learning and ease-of-use, something which I think is important enough to shirk Java and C as a whole.

No comments:

Post a Comment

Blog Archive