Meh, I like Java. Like, I actually enjoy programming in it. Some key reasons: 1. IDEs are not a crutch. They're a useful tool. Anyone who talks about expressiv

Meh, I like Java. Like, I actually enjoy programming in it. Some key reasons: 1. IDEs are not a crutch. They're a useful tool. Anyone who talks about expressiveness or efficiency in Ruby but discounts IDE help is a hypocrite. You learn the tools you have. Refactoring large methods, extracting interfaces, mass renaming with guaranteed safety -- those things actually matter when you learn to use them. 2. Ant is dead. Hibernate is dying. Spring XML config is largely dead. Much like the perf argument, most of the bad impressions people have of it are based on years-old issues. 3. Tools like Spring Boot and Dropwizard have made it so a Java REST service is smaller than a RoR one. 4. Gem upgrades can be backwards incompatible, so once your app is of a certain size, your framework support becomes very rigid and brittle. 5. Twitter left Ruby because of perf issues. drops mic 6. Active Record ~= Hibernate. Hibernate can be configured with annotations, so leave the XML out of this. You still have n+1 and over-selection of fields by default. 7. Global interpreter lock. 'Nuff said. 8. The actual argument used by DHH wrt performance was, 'Ruby is fast enough' -- if the Java community tried that, it would be an endless mocking parade. I could go on, but won't. I don't care if others leave Java, just means more work for me. Hell, replacing shitty rails apps and replacing them with reasonable java apps is a good consulting business :)