Ruby, My Dear
More on JRuby and Sun
Last week, you'll recall the surprise announcement that the two primary JRuby developers are joining Sun. It's a particularly apt choice given the interest in Ruby from Java developers: it seems the one agile language with the greatest appeal to the Java mindset (I think Michael Ivey told me five years ago that I should give Ruby a try, that it was a natural fit for Java programmers). And honestly, would we be pining for closures in Java if they were they were the highlight of some uglier, scale-proof language like PHP or Perl?
So what are the JRuby guys going to be doing? In JRuby Love, Tim Bray says the JRuby guys will be working on JRuby full-time, but "they also have a mandate to think about developer tools. Right now, developers who use dynamic languages like Python and Ruby are poorly served, compared to what Java developers have."
That rubbed ONJava blogger Timothy M. O'Brien the wrong way. In Sun hires JRuby Developers (to focus on developer tools?), he wrote:
WRONG, has he ever used RadRails, Eclipse, Komodo? Probably not, at Sun, the only IDE that exists is NetBeans, and I certainly hope tihs doesn't mean that Charles Nutter and Thomas Enebo and going to be forced to work on the NetBeans team. I fear that might be the case. The one common theme I've noticed from Sun over the past few years is that they spend an irrational amount of time hyping NetBeans as the answer to every problem. I hope this is good news, and I hope that they didn't just hire the JRuby guys to be semi-junior developers on the NetBeans team.
Charles Nutter responded to this, which O'Brien quoted at length in a follow-up blog, Charles Nutter Responds: "our full-time responsibility is a solid JRuby 1.0". Nutter says:
Totally false. The principals at Sun