3 ms·
But it's boring to use. I've been trying to figure out what you meant by that. I noticed you had a tweet a couple of weeks ago: I have decided that JRuby is o
by sofal 17y ago
But it's boring to use.
I've been trying to figure out what you meant by that. I noticed you had a tweet a couple of weeks ago:
I have decided that JRuby is officially boring. It "just works" in a terribly predicable manner, and the Java integration has no surprises.
It sounds like you use "boring" with some good as well as some bad connotations. Is there a blog post or something where you explain this?
- bensummers 17y agoI can see how that's ambiguous. I mean this in a totally good way. Moving to a new implementation of a language interpreter should not have any exciting surprises, it should just behave in the same way as any other implementation. JRuby succeeds remarkably well in working exactly as the MRI implementation. Therefore I consider "boring" to be high praise. What's exciting is what it enables, which is real threading and java integration. But that's another story, and I do intend to write a blog post on it soon.