Friday, December 09, 2005

The bad snake

"Python programming: be the snake, eat the ruby, and throw the perls to the C" this was the topic of today when I went into the #python channel on undernet. I totally support this.

I've been into python for some time now; Perl is ok and cool; though most will say its the thingy. Well for me I think it does not matter what language you use. Its getting it done, and how fast you get it done, and the maintainability. As for my work; I often have to write small scripts to do odd jobs on the systems; and I found Python to be a life saver. Its easy to develop in Python, its fast to develop and it looks neat! Yeah! Bloody neat compared to Perl (most) scripts.

Last night I got some small scripts done again; to automate the process of mailing all staff bills to their emails as html mails. This was simple, but had to do a lot of odd stuff that might have taken me lot of time if "I" were to do it in Perl or other shell scripts. Plus Python scripts run on windows, *nix and on my phone as well. So its a good toy language too, to play around with.

I have not done major big projects with Python and which involves heavy usage for the GUI's and DB's but I think it's high time I should do that. So next question is Microsoft coming up with a "Python#" ?!? hehe

3 comments:

Anonymous said...

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!

faraz said...

i guess it already exists

http://www.zope.org/Members/Brian/PythonNet

jaa said...

A python# developement environment from microsoft isn't *that* bad an idea actually. Microsoft took the likes of OCaml and made functional programing a bit cooler. Mu humble opinion...

And yes, I agree wholeheartedly on your views on python.