Ryan Tomayko on The Pending Ruby/Java Co-op:
You can take Java’s crippled OO foundation, enterprise scalability, vendor supported JEE containers and just throw it all out the window: I don’t care. Memory management is the reason to consider using Java over C right now.
So why Java? Ryan has a lot of good arguments, I want to add two more:
- Venn. Most of the developers I know who are working with or looking at Ruby have a Java background. That’s anecdotal evidence, but I think the cross-over is significant. Check out some of the Java resources, and you can gauge that interest for yourself.
- Ears. Looks like Sun is listening to this one, and listening well.
And then, there’s timing. We all believe the best technology choices are made on their own merits, but sometimes it’s just a matter of being in the right place at the right time. I think that’s the no. 1 reason Java and Ruby might soon exchange vows.