You're pretty much right. The problems really start when you work in an enterprise but you are on a very small team (no greater than 2, but almost always just

You're pretty much right. The problems really start when you work in an enterprise but you are on a very small team (no greater than 2, but almost always just me), and your boss wants it done in Java for no real good reason. Another problem is that using most Java frameworks is not as simple as including a JAR in the classpath. They require different amounts of config files and boilerplate start up code. The ultimate problem is that when you've had a taste of metaprogramming, real closures, or some other feature that Java lacks, you find it extremely irritating to lose that power just so that you can say you wrote it in Java. PS. Limewire is a client Java app (or at least loads and looks like one).