Lonely Lion

Chris McAvoy likes kites

Why Python 3k Shouldn't Be Ruby (and a mention of Erlang)

with one comment

Just a quick response to this write up on the lack of growth in Python 3000. Python 3000 really isn’t the giant sea change that I thought it was going to be. Most of the significant work is under the covers, optimizations that will benefit me without me necessarily knowing it. The author of the above post (I’m sorry, I couldn’t find the author’s name), like me, is a fan of Ruby and Python. I think he wants Python 3000 to take on some of the traits we both love about Ruby (extreme flexibility, cleverness, many ways to do it). I know where he’s coming from, but that wouldn’t be very ‘Pythonic,’ it would be ‘Rubyonic.’

One of my favorite bits about being a polyglot is the differences between languages. What’s the point of making Python like Ruby? What’s the point of making Perl like Python? If everyone is sort of doing the same thing, where’s the fun in learning new stuff? I love Python, I love Ruby, I even love Perl. Let’s preserve their differences. Python doesn’t want you to muck around with the syntax, Ruby does. Use Ruby when appropriate, use Python when appropriate. Right?

Speaking of polyglotism, I bought that Prag-Prog Errrrrlang book over the weekend. All variables are constant, and must start with a capital letter. How’s that for balls nuts? Woo hoo! Viva la Different!

Written by Chris

March 30th, 2007 at 8:10 am

Posted in Erlang, Perl, Perl6, Python, Ruby

One Response to 'Why Python 3k Shouldn't Be Ruby (and a mention of Erlang)'

Subscribe to comments with RSS or TrackBack to 'Why Python 3k Shouldn't Be Ruby (and a mention of Erlang)'.

  1. well put!
    it took me a long time to learn this: don’t fight the system.
    i browse the python-{dev, 3000} archives:
    sometimes i feel really bad for guido.
    many python (newbie (?)) users find out about Ruby or Lisp
    and want to implement what cool over there, in python.

    i know of the pragprog erlang book, but after you
    mentioned it, i visited their site and came across
    this:
    http://pragmaticprogrammer.com/articles/erlang.html

    he talks about ericsson’s downtime being 9 9’s
    that’s (if my calculations are correct)
    1 second of downtime every thirty years!!!

    cool!

    sri

    3 Apr 07 at 10:25 am

Leave a Reply