Sun's JRuby Team Jumps Ship To Engine Yard 77
Posted
by
kdawson
from the just-in-case dept.
from the just-in-case dept.
itwbennett writes "'To be honest, we had no evidence that Oracle wouldn't support JRuby, but we also didn't have any evidence that they would,' said Charles Nutter, explaining why Sun's entire 3-member JRuby team will be leaving the company to work for application hosting company Engine Yard. Nutter called getting hired by Sun about two-and-a-half years ago and being given the chance to work full time on JRuby a 'dream come true.' And said that the decision to leave Sun came down to making sure 'JRuby will get to the next level.'"
. . . . and heeeerreesss Genghis (Score:1, Interesting)
Some will prosper with Larry,
Some will die with Larry,
Some will jump from Larry,
Some will be pushed by Larry.
The one thing that won't happen is the question not getting asked, and it will be "are you good/viable/strategic(insert favourite acronym here) for Oracle, not are you good for Sun".
they won't die wondering !
Re:So lemme make sure I got this right... (Score:4, Interesting)
The interesting bit... (Score:5, Interesting)
...is that now EngineYard has full-time folks working on Rubinious, JRuby, and Ruby 1.8.6. It's Ruby implementation central over there.
Re:So lemme make sure I got this right... (Score:5, Interesting)
I'll one up that: Based on my experience in several software engineering companies (video games), my policy is now to find a new job ASAP when your company gets bought out, even if they DO say they want to keep you! (That being standard operating procedure -- not hearing that is the equivalent of an immediate pink slip.)
Engineers can only really advance by switching companies. Definitely best to jump ship when some people are talking about you and you have some leverage, no doubt about it.
Re:JRuby is a failure. (Score:3, Interesting)
Benchmarks are actual observations -- what we in the real world like to refer to as "science".
If you've got a benchmark of a larger application that you'd like to share that shows just how much the JVM sucks, I'm definitely curious. Ruby 1.9 works well for me now, but I'd been considering JRuby as a performance boost. If you can show me it's actually a failure, that would save some time.
Re:JRuby is a failure. (Score:2, Interesting)
Not to mention things such as perl5i [github.com] which tries to aggregate most of what is known as modern Perl.
Perl is an evolving language and Perl code from 8 years is very different from modern Perl code.