It kind of depends on a history of a project. If the team is most familiar with Java, and all the processes work with Java, then that would make sense. I actu

It kind of depends on a history of a project. If the team is most familiar with Java, and all the processes work with Java, then that would make sense. I actually started off as a Java programmer, and in the last couple years switched to rails. I found Java to be incredibly verbose. I don't know if things have changed, but in addition to declared exceptions, we constantly had to be catching runtime exceptions like NumberFormatExceptions, etc. I really find Java to be incredibly verbose. Ruby on the other hand is syntactically cleaner, but I do miss compilations to catch some of my errors instead of in run time things blowing up. I'd say the bigger question is Rails or J2EE? J2EE's overcomplex frameworks really wanted to make me pull my hair out (but I'm hoping the newer Java frameworks have fixed it since). Digressing a bit, Rails is nice, but only if your application fits that paradigm.