Speaking of Simon, when I invited him I was preparing a Perl session. The interesting, was his answer: should I talk about Perl or Ruby?
I know ruby already (well, I know it exists, and I did see some code examples) but I wasn't expecting this "change" from Simon.
When I compile Ruby, I love to have a autoconf/automake installation scheme (shame on Perl) but I hate not having tests (shame on Ruby).
I still didn't have time to learn Ruby, but can you guys, who read this, point where Ruby is better than Perl, and where Perl is better than Ruby?
Where is Ruby better.... (Score:1)
Re:Where is Ruby better.... (Score:1)
curious (Score:3, Insightful)
I'm always very curious of what people find to be so excellent in autoconf/automake (*). If you are referring to the Perl Configure by default being interactive (shame on GNU configure), I can't really see what GNU configure has that either Configure -des or configure.gnu don't have.
(*) Personally I find the GNU configure/build system to be an abomination.
Reply to This
Re:curious (Score:1)
In fact, I do not mind to have iteraction (ok, configure for Perl as too many iteraction :-)). It is true, also, that Perl Configure has many interesting lines :-)
Although I do not think that GNU configure/build system is an abomination (of course it could be better, but I think they accept suggestions) I like to have a package, and know how to install it (to have a recipe). configure && make && make check && make install...
Ok, you can say perl is similar (Configure && ma
Ruby vs Perl - the short version (Score:2)
=====================
Speed
Unicode support
Where Ruby is better:
=====================
OO and Exception handling
Extensions
Threads
Syntax is arguable (just talk to Python people!), but I prefer Ruby's.
Re:Ruby vs Perl - the short version (Score:1)