This just in: Ruby actually fast now

Apple's version of Ruby could already, at this early stage of its development, be about three times as fast as the fastest Ruby implementation available elsewhere.^[1]

But that's still slow as fuck, right?
___
_{[1] - http://developers.slashdot.org/article.pl?sid=09/03/29/207240}

>>1
3 * infinity is still infinity

YARV is already a reasonable improvement, but it's a dynamic language after all.

YARV isn't really a valid acronym.

YARV = YARV Acronym isn't Really Valid

>>1
the fastest Ruby implementation
There's no such thing.

>>2
3 * infinity is still infinity
I think you mean ∞/3 = ∞.

(∞+∞)-∞ = 0

>>7
How do you do the backwards 8 symbol?

>>9
backwards-mode

>>1
it's still slower than FIOC 3000, which is 3000 times slower than regular FIOC.

Why exactly was Ruby so slow in the first place? Shitty compilers?

>>12
ruby doesn't use compilers. it's interpreted. and the interpreters are written by a bunch of php „proogrammers“.

>>12
It started out as a hobby language for writing shell scripts. The author didn't care much about speed, so even though he wrote it in C, it wasn't designed with fast execution in mind, and so it was merely "good enough." He added features for years with no regard to how much work it would take to reimplement everything.

Then the killer apps like Rails came along, and used all those features he'd been adding, so even when people started implementing fast versions of Ruby, there were so many weird edge cases that none of the apps worked right. So, it's taking forever to get a fast, stable, production-ready Ruby out the door.

If the core of the language had been smaller, tighter, and more consistent, it would have been trivial to drop in a replacement interpreter with a faster design.

>>13
Rails is written by PHP /prog/rammers

Ruby is written by people who used to write C++ for a living

>>12
It's compiled with the same shitty old version of GCC that compiles all the other shitty and broken C software that had diarrhea all over your hard drive. It's slow because it's dynamically typed and you can subclass any subclass so you can iterate while you see what I did there.

>>14
So would it be fast if it was written in C++?

>>17
It IS written in C/C++

>>14
he wrote it in C
>>16
It's compiled with the same shitty old version of GCC that compiles all the other shitty and broken C software

Based on the previous two statements that have clearly been stated clearly, I have come to the conclusion and shall announce for all to see/hear: >>18 was TROLLe by >>17.

Thank you.

>>19
>>14 and >>16 obviously meant to say "C/C++" so I don't know what you're talking about.

>>21
STOP BUMPING SHITTY THREAD!!

>>16
This issue can be fixed by using JRuby, which leverages the power of the Java Virtual Machine to compile down to native code (JIT) when appropriate.

>>22
Yet, it's still Ruby, so it's still slow as fuck

^{Back to /b/, ``GNAA Faggot''}

<