Thursday, October 12, 2006

ESR's take on Python

This is probably the third time I've run across this article, but every time I skim it and smile at how well he sums it up for me:

So the real punchline of the story is this: weeks and months after writing fetchmailconf, I could still read the fetchmailconf code and grok what it was doing without serious mental effort. And the true reason I no longer write Perl for anything but tiny projects is that was never true when I was writing large masses of Perl code. I fear the prospect of ever having to modify keeper or anthologize again -- but fetchmailconf gives me no qualms at all.

The same things happen to me: About half way through my masters degree, I realized that I couldn't stomach writing significant amounts of new code in C++. So I switched to python for a few projects. I rarely code anymore, it's just thesis writing. But sometimes I need to generate new results, new figures, something that I can't generate with my current programs. When this happens and I can use my python program ... I don't have any concerns about doing it. I fear the day that I have to maintain my C++ program that I wrote.

No comments: