From: Colin Sampaleanu <cas@...>
Date: 2001-03-06T12:43:09+09:00
Subject: [ruby-talk:12075] Re: Not Ruby, for me, for the moment at least

Speaking from my own perspective, I wouldn't underestimate how big how much
impact the (pretty much richer) library of code (internal and external) that
Python has available to it would have in making people choose Python over
Ruby. I have used Python here and there over the last year, preferring it to
Perl since Perl always felt like a big mess to me, and Python felt cleaner.
On the other hand, Python's roots are pretty evident, and I was never
completely happy with it. When I first took a serious look at Ruby about a
week ago, it just felt 'right' (I might even say beautiful). I will try to
use it where I can, and try to contribute as much code as I can, but I have
a feeling I will still be using Python for many things. My primary use of a
scripting language is to save time. If I need to get something going, and I
can find Python code that helps me get most of the way there, but have to
implement similar code in Ruby, most of the time it will be a no-brainer due
to time constraints. Things like nice IDEs (along with PythonWin there are
new Python IDEs from PythonWare and theKompany) also have an impact on
productivity, so for me at least, are a factor.


> -----Original Message-----
> From: nosuzuki@e-mail.ne.jp [mailto:nosuzuki@e-mail.ne.jp]On Behalf Of
> Clemens Wyss
> Sent: Monday, March 05, 2001 2:40 AM
> To: ruby-talk ML; ruby-talk@netlab.co.jp
> Subject: [ruby-talk:11997] Re: Not Ruby, for me, for the moment at least
>
> ...
> Python definitely is a good choice, but as of this writing the only
> reasons for choosing Python over Ruby are (IMHO): - CORBA-binding(s)?
> OmniOrbPy, fnorb. - better Win32(API) support? Thanks to Mark Hammond
> - PythonWin? IDE with syntax higlightning and (visual-)debugger.
> - speed?
> But as you didn't mention any of these as a requirements for your project
> I (and possibly others too)  don't see why you have made this decision.
>