August 21, 2007
Why would a Java Shop want to use Ruby?
I think it's an interesting question. Why would a Java shop want to use Ruby? Some would say that there's no need. I don't have a problem with that decision if it is well-informed. However, I suspect that many people in traditional Java groups do not know how they could benefit from Ruby.
At OSDC in Brisbane in late November I'll be attempting to show that there is a potential to improve a Java shop's business success by augmenting existing skills and techniques with the use of Ruby.
Now that my proposal has been accepted, it is time to start fleshing out my paper.
Posted to Java, Ruby by Keith PittyI don't believe there would be an real technical benefit. There may be a productivity boost, but when you really consider how much time is used by developers, QA, etc... to bring in a new technology, chances are the net won't be that great. I think the best argument for Ruby is that your developers want it. If the developers are yearning for new technology, it's probably worth considering. Happy developers code more and code better.
Posted by: Norman Richards at August 22, 2007 7:22 AMNorman,
When you say "I don't believe there would be any real benefit", I wonder how much you have explored Ruby. I acknowledge your comment about the cost of the learning curve. However, if we always adopted that stance we would never accept any benefits of innovation. I'm sure you'd prefer Java developers to use Seam than still be using pure servlets as they were before the advent of JSP! And I'm sure you would agree that EJB 3.0 is a huge improvement on the original spec.
I throughly agree with your assertion that "happy developers code more and code better." In my humble opinion, opportunities for programmers to learn should always be balanced with the cost/benefit of adopting new technologies.
Posted by: Keith at August 22, 2007 11:10 PM