Hacker News Reader

It would be nice to see some progress made on the interpreter but I think it's to Ruby's credit that the language design hasn't changed that much in the last several years. A lot of the activity on the Python side has been fixing things that weren't well thought through in the first place.

View on HN

You don't seem to understand that "language design hasn't changed" tends to preclude "progress made on the interpreter".

Python's warts have been fixed and will continue to be fixed. I cant really say the same for Ruby, especially for MRI.

Honestly, I'd say the opposite is true. The more the language design changes, the more implementor time is going towards servicing the changes and not squeezing the fat out of the implementation.

That being said, the two often occur together because changes are exciting and attract effort.

I don't see how that follows at all. If the biggest issues with Ruby are performance and memory management how does changing the language spec help fix that? If anything a stable language spec should help nail down the bugs in the engine.

Reply on news.ycombinator.com