From: ReggW <me@...>
Date: 2006-06-03T20:37:58+09:00
Subject: Re: Speed of Ruby program != Speed of Ruby language (was Re:

Ryan Williams wrote:
> I think Dave's point is that it's irrelevant what Ruby itself is
> implemented in.  The problem is that whenever performance dicussions
> come up, instead of discussing how to imrpove the speed of
> Ruby-the-language, people instead talk about how easy it is to use
> languages other than Ruby for programs that are supposed to be fast.
> 
> Dave wants to talk about how to make fast programs that are completely
> written in Ruby.  And I do too, though I have little to contribute
> except to perhaps bring the discussion back in line.  Maybe we could
> talk about improving the speed of the Ruby implementation, or about
> improving our use of the language.  But can we have a discussion where
> we pretend for a moment that we don't all want to run out and
> implement things in C?
> 
> -RYaN

I agree with Dave and Ryan.

This discussion should be about how to make "RUBY's" performance faster 
when you are using "RUBY", not C.

I'm very well versed in the C/C++ language and I think C is a great way 
to "extend" the language of Ruby, but C should not be a requirement to 
get great performance from Ruby, this should already be available.

So let's talk about what can be changed about Ruby to make it faster 
out-of-the-box?

I don't know the internals of Ruby (and I shouldn't have to...yet), but 
how about we start with the engine, rubyw.exe, are there some area's 
here that can be improved?


Thanks

-- 
Posted via http://www.ruby-forum.com/.