From: Tom Sawyer Date: 2002-09-19T15:06:26+09:00 Subject: Re: Python the new Lisp, what about Ruby then? who's bashing? just stating an opinion. time will prove me right or wrong. it dosen't really matter anyway. now does it? and who knows? perhaps some super language will come along a lay a path of dead languages behind it. ruby to ruby? now that is a pointless comparision :) hey, if you don't compare languages, what's the point of choosing one over the other in the first place? -transami On Wed, 2002-09-18 at 22:38, bbense+comp.lang.ruby.Sep.18.02@telemark.stanford.edu wrote: > -----BEGIN PGP SIGNED MESSAGE----- > > In article <1032407726.16274.346.camel@silver>, > 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. > > - - Lisp started around 1956 and has been widely used since 1960 > or so. It's got a long head start. > > > > >i think ruby has greater potential for sticking around, and perhaps is > >the successor of python to which i refer. > > > > - - Repeat after me... > > Ruby is the new Ruby..... > > Pointless comparisions are a waste of time. Python/Perl/Foo > bashing merely makes you look well, un-Ruby like. > > - - Booker C. Bense > > > > > > -----BEGIN PGP SIGNATURE----- > Version: 2.6.2 > > iQCVAwUBPYlQ32TWTAjn5N/lAQHh+wP+ONJp+detA/HNp3AeGTkP5IpFgb3AjSMr > yl3zQ2gondHIM+y91ZL5CAMbnAN+wEMzwgs3FEL2D8ZW2fJ/R63G5jhYJb3CniM5 > JoOkjs0UR1UOSRUZTKXpscLQJlDfxtNtAjA4QzS1cwu+BmCTW/N52H7qwoZPdJ1V > 2IJWJqDp+Fc= > =kdDp > -----END PGP SIGNATURE----- > -- tom sawyer, aka transami transami@transami.net