3 ms·

It seems that EY is going to focus on jruby instead of rubinius.

by jshen 17y ago

jamesbritt 17y ago
Where in the world did you get that from?
- gaius 17y ago
  It's a reasonable assumption given that they're laying off Rubinius developers and hiring JRuby developers. Tho' you'd be hard-pressed to do that in the UK, an industrial tribunal would wonder why you didn't even attempt to cross train them and offer them jobs doing JRuby.
  - jamesbritt 17y ago
    http://www.engineyard.com/blog/2009/engine-yard-adds-jruby-support/ http://www.engineyard.com/blog/2009/engine-yard-adds-jruby-s... "With JRuby support, our ongoing maintenance of the 1.8.6 branch of MRI and our continued sponsorship of Rubinius, ..." Emphasis mine.
  - gaius 17y ago
    Seriously, tho' this is what's wrong with the IT industry. Meta their job descriptions up one level and their roles are all "Ruby implementor". Just one's flavour of the month and one isn't. Imagine your company was switching from Linux distro A to distro B and simply sacked all the sysadmins and hired ones with a different "certification". Engine Yard would get eaten alive for this anywhere in Europe.
    - daeken 17y ago
      The challenges in implementing your own VM and implementing a dynamic layer on top of the JVM are entirely different. It's not like moving from one distro to another, it's like moving from Linux to a custom RTOS and expecting your existing kernel people to do the job as well as existing RTOS developers.
      - gaius 17y ago
        They're certainly smart enough to, so why not? Like I say this is a problem across the IT industry, hiring managers want buzzword-compliance with the very latest thing, and never mind that the actual value in any IT organization is in the people that know the business and have a track record of identifying and solving problems in it. The job market's not great right now but individuals have longer memories than organizations, and companies that show no loyalty to their people now are going to pay over the odds for talent when the market picks up.
        daeken 17y ago
        It's a completely different problem set, a completely foreign codebase, and a completely different platform entirely. In addition, it's not their baby; would you like it if your company decided you're going to work on a competing project to the one you founded, while you're presumably working on your project in your spare time? They made a perfectly logical decision.
- deleted 17y ago
  [deleted]

It seems that EY is going to focus on jruby instead of rubinius.

by jshen 17y ago

It seems that EY is going to focus on jruby instead of rubinius.

jamesbritt 17y ago

Where in the world did you get that from?

gaius 17y ago
It's a reasonable assumption given that they're laying off Rubinius developers and hiring JRuby developers. Tho' you'd be hard-pressed to do that in the UK, an industrial tribunal would wonder why you didn't even attempt to cross train them and offer them jobs doing JRuby.
- jamesbritt 17y ago
  http://www.engineyard.com/blog/2009/engine-yard-adds-jruby-support/ http://www.engineyard.com/blog/2009/engine-yard-adds-jruby-s... "With JRuby support, our ongoing maintenance of the 1.8.6 branch of MRI and our continued sponsorship of Rubinius, ..." Emphasis mine.
- gaius 17y ago
  Seriously, tho' this is what's wrong with the IT industry. Meta their job descriptions up one level and their roles are all "Ruby implementor". Just one's flavour of the month and one isn't. Imagine your company was switching from Linux distro A to distro B and simply sacked all the sysadmins and hired ones with a different "certification". Engine Yard would get eaten alive for this anywhere in Europe.
  - daeken 17y ago
    The challenges in implementing your own VM and implementing a dynamic layer on top of the JVM are entirely different. It's not like moving from one distro to another, it's like moving from Linux to a custom RTOS and expecting your existing kernel people to do the job as well as existing RTOS developers.
    - gaius 17y ago
      They're certainly smart enough to, so why not? Like I say this is a problem across the IT industry, hiring managers want buzzword-compliance with the very latest thing, and never mind that the actual value in any IT organization is in the people that know the business and have a track record of identifying and solving problems in it. The job market's not great right now but individuals have longer memories than organizations, and companies that show no loyalty to their people now are going to pay over the odds for talent when the market picks up.
      - daeken 17y ago
        It's a completely different problem set, a completely foreign codebase, and a completely different platform entirely. In addition, it's not their baby; would you like it if your company decided you're going to work on a competing project to the one you founded, while you're presumably working on your project in your spare time? They made a perfectly logical decision.
deleted 17y ago
[deleted]