From: Jacek Podkanski <jacekpodkanski@...>
Date: 2002-09-19T20:00:08+09:00
Subject: RE: Python the new Lisp, what about Ruby then?

Tom Sawyer wrote:

> On Wed, 2002-09-18 at 21:37, Mike Campbell wrote:
>> > ruby though just may gain as great a heritage as lisp due to its highly
>> > OO nature. but python? flash in the pan.
>> 
>> I don't use Python, but I'd hardly call it _that_.  It is quite popular,
>> and
>> doing Real World Stuff (tm).  Seems to me hardly faddish.
> 
> well, i exagerate. but you get my meaning. i'm sure python dosen't have
> the staying power of lisp. lisp will probably be with us for all time,
> while python will be superceeded.
> 
> i think ruby has greater potential for sticking around, and perhaps is
> the successor of python to which i refer.
> 
Choosing Ruby I made comparison to other languages, mostly python, Python 
seems to be better documented, more popular, has more modules etc.
Yet I chose Ruby. It wasn't pointless comparison because I have language 
that will stay with me for very long time. 

It's bit like shopping before you invest your time and effort in a new 
language you'd better make good comparison and choose wisely. Then the 
language will serve you for long time.

But if making such choice you just follow fashion comparisons are pointless.

Comparing with other languages can teach you a lot. I don't mean here some 
shallow list of features but trying to learn some of the language and see 
how things can be done in a different way, or even learning new way of 
thinking. 

Perhaps Pragmatic Programmers rule 'one new language a year' can give you 
hints how useful such comparisons can be.

I recently started to learn some Lisp. Ruby will be my main language, but 
believe me, this experiemce will improve my Ruby programming.
-- 
Jacek Podkanski