Your misrepresentations of my position and attacks on me are unbecoming.
Jamal
···
--Original Message--
Sent: Friday, July 14, 2006 12:36 PM
To: ruby-talk ML
Subject: Re: How to speed up ruby and make it as fast as possible
Jamal Mazrui wrote:
In answer to the multiple messages recommending that I learn C or
Assembler as the solution for performance, it appears that you did not
read my lips: I want to use Ruby, not a typically tedious, often
verbose, yet also cryptic strongly-typed language!
Fine, use Ruby. But if performance is critical then you will be
disappointed. You have been warned but you are clearly not prepared to
listen.
I have read
tutorials on such languages before and found their nature to be
counter
to my desire for rapid application development.
What happened to your desire for performance. Is this now secondary to
laziness?
I understand that no
single language is superior in all criteria, and that trade-offs exist
between ease of development and speed of execution.
The you will just have to accept the trade off between ease of
development and performance. If you really really really want
performance then write it in C.
The trend in universities, by the way, is away from teaching native C.
Instead, Java and C# for the .NET platform are taking over. That
argues
against learning C specifically to compensate for Ruby's weakness. If
I
were to invest in the hundreds of hours to become facile in a strongly
typed language, C# would be the one most likely to benefit my
productivity and career. (As much as I like Ruby, it is a means to an
end for me, not an end in itself.)
I find it hard to understand how someone can call themselves a
programmer and then claim that learning C is too difficult. It's not as
easy to use as Ruby, but it could hardly be called difficult. Being a
programmer, for me, is being in a constant state of learning. Perhaps
for some it is just a 9 to 5.
Jamal