That's some bitter coffee

As a Java developer, sometimes I look at the toys that the .NET developers get to play with with a great lust in my heart. Especially at times like today. Java has terrible problems with resolving dependencies that .NET doesn't have, thanks to its Global Assembly Cache. Every so often you run into problems in large Java environments where you have two versions of the same library. One effectively kills the other because Java has no way to say "this is version 1.0," "that's version 2.0" and then intelligently assign them to each program as needed. Nope, it's all flat and even, meaning 1.0 or 2.0, but there is no coexistence without some hackery. This is the one thing that drives me up the wall with Java sometimes, and is why I now play around exclusively with .NET on my own time. Java really needs to have some changes like that made.