They were employed by Sun, not IBM, and already worked on JRuby full time. I think this was more about integration into the Ruby community as well as getting a good JRuby deployment option in place at EY, as well as uncertainty over Oracle's acquisition of Sun.
Edit -- Charlie Nutter on jruby-user: "The primary reason for leaving was the high level of uncertainty involved."
Good catch, but still. If they knew Sun had a JSR waiting to leave the door that would essentially put their pet project on the map, it makes perfect sense to go with a more cutting-edge vendor who would care for it, maybe negotiating better pay, or even waiting another year before launching your own support-shop.
I don't understand what you're getting at. Why did you emphasize "only" above? Are you trying to imply the JRuby guys are leveraging some kind of inside knowledge? You know this JSR's been in the works since early 2006, right?
The JSR will certainly improve JRuby's speed and simplify development, but I don't think it will affect adoption (and actually I'd say JRuby was already on the map, given that it can run Rails and handily beats Ruby 1.8 performance-wise).
JRuby's real problem is that the Ruby community is wary of anything with a J in the name that's sponsored by Sun. Hopefully this will help out with that.
Comments
They were employed by Sun, not IBM, and already worked on JRuby full time. I think this was more about integration into the Ruby community as well as getting a good JRuby deployment option in place at EY, as well as uncertainty over Oracle's acquisition of Sun.
Edit -- Charlie Nutter on jruby-user: "The primary reason for leaving was the high level of uncertainty involved."
Good catch, but still. If they knew Sun had a JSR waiting to leave the door that would essentially put their pet project on the map, it makes perfect sense to go with a more cutting-edge vendor who would care for it, maybe negotiating better pay, or even waiting another year before launching your own support-shop.
I don't understand what you're getting at. Why did you emphasize "only" above? Are you trying to imply the JRuby guys are leveraging some kind of inside knowledge? You know this JSR's been in the works since early 2006, right?
The JSR will certainly improve JRuby's speed and simplify development, but I don't think it will affect adoption (and actually I'd say JRuby was already on the map, given that it can run Rails and handily beats Ruby 1.8 performance-wise).
JRuby's real problem is that the Ruby community is wary of anything with a J in the name that's sponsored by Sun. Hopefully this will help out with that.