I was recently asked for a list of "hard problems" a Ruby implementation really needs to solve before reporting benchmark numbers. You know...the sort of problems that might invalidate early perf numb...
Mike Dalessio's profile photoDavid Wood's profile photoCharles Nutter (headius)'s profile photo
"So you want to optimize Ruby" ... Hrm, actually I'd much prefer if +Charles Nutter handles optimization. I'm happy to be a consumer. ;)
That was... illuminating, to say the least. I used to think it was indifference, but now I get the sense, looking at the laundry list of features and their consequences, that writing of MRI must have been like an act of war on the CPU.

I think you've written the favorite article of the day for the chipmakers in the audience. :-)
Lots of fun challenges, for sure. And it seems the Hotspot guys agree...they take my complaints about optimization failures as challenges. The future looks bright.
Add a comment...