An Interview With Guido van Rossum

An anonymous reader submits "The folks over at artima.com have finished posting a 6 part interview with Guido Van Rossum, Python's creator and Benevolent Dictator for Life. The interview covers topics ranging from Python's origins and design goals to increased productivity to runtime typing." (We linked to this series of interviews before as well.)

Comments

Re:Mr Rossum

[sigwinch]

I've been using Python for quite some time now...

Translation: five minutes.

...and I've found it vastly superior, ... functionally... to both Perl and PHP.

Duh. Perl isn't very good for functional programming. And PHP? Ha! It's barely a procedural language. Have you tried Scheme+? It's fully functional, and uses brackets instead of parentheses so it's vastly easier to read.

One knit, though.

<sigh> A veiled reference to the long-running dispute between the Perl lib_sock camp, and the proponents of PySock. Get over it. Modern implementations are comparable in performance, and the API problems in PySock were fixed long ago.

Why on earth make whitespace vital to the compiler?

One of the greatest insights in modern physics is that the vacuum is an active player. Defining the language with space as well as substance provides an independent structure by which to understand your programs. I saw at the last COMDEX that Rational is working on a tool that lets you graphically design and refactor Python code using Feynman diagrams.

For business reasons I have to edit my programs in Windows but run them on Linux.

Hello? Wine! Duh!

Editing out all those ^M's is a big pain.

This is why experienced Python programmers store their programs as XML. It's disgusting to see someone waste time on platform incompatibilities in this day and age. Remember: write once, run everywhere.

Running everywhere is good exercise, anyway. Not only can you proactively reengineer core business centers, you can get that ripped look so popular in today's nudist conference rooms.

Re:Mr Rossum

[trouser]

There's no shortage of editors which will save files properly. If I ever have the misfortune to find myself trying to work on a Windows machine I download vim. Or you could try winpython. I suspect it has the option to save not broken files and it also does neat code completion stuff.

Why make whitespace vital ? Why use braces to mark a block in code ? Why use line numbers ?

You have to have some way of letting the compiler/interpreter know what's inside/outside a for/if/while etc. block. The whitespace thing takes a little getting used to but it follows the indentation rules you probably should be applying to your code anyway in the interests of producing readable and hopefully maintainable code so it shouldn't be too great a hardship.