Java can not manage memory marshaling between win32 apps and managed code. In Java, you need to message pass with pipes, and its a pain. In Linux Piping is re

Java can not manage memory marshaling between win32 apps and managed code. In Java, you need to message pass with pipes, and its a pain. In Linux Piping is really fast, but in Windows, Piping is slow. I really like being able to code C++ and C# in the same solution, but in different projects, while being able to step through all layers of the code. Remote Debuging, and RPC calls are way better in .NET Also if you are doing XML, and Web Service calls (soap, get, post) .NET includes the functional layering and interface segmentation to access each of the protocols independently or together. In my opinion, if you want to set up some sort of transactional API, .NET has leaps and bounds better performance and professionals level tools. If you are trying to hack something together, .NET has a large learning curve, and requires disciplined programing to get any practical use out of it.