In Java, you’d say new Pony("black"), and the pony is made by Pony(String color). In Ruby, you’d say Pony.new("black") and the pony-maker is initialize(color). In Python, you’d say Pony("black") and the pony-maker is __init__(self, color). I wonder which is best? Does all this seem kind of ad-hoc? Anyhow, in real life, a Java programmer would start with an AbstractEquineBreederGenerator and work from there. And for Ruby you’d be able to say mySpecialPresent.get do | pony |, and it would clean up the pony poop for you (but the pony would be named Kurofune). Python programmers are Serious Men and Women who Don’t Have Time For Ponies. [Update: The email is already swirling in. Stand by for another virtual comments section.]


ongoing
software · G & M · Dad author · colophon · rights
picture of the day
Around July 20, 2006: The DOM Song · Lebanon Roundup · The First Joke · Upcoming Gig: RubyConf · Upcoming Gig: OSCON

What?
· Technology (61 fragments)
· · Coding (72 more)


Serif · Sans-Serif
I work at Sun Microsystems. The opinions expressed here are my own, and neither Sun nor any other party necessarily agrees with them.