Microsoft's monopoly really stood in the way of Java being used for large, stand-alone applications; almost as much as Java's lack of maturity at the time. Why bother starting at ground zero with office and personal productivity products? Why bother starting at ground zero period?
That's all changing dramatically as the API sets expand and mature. Java is now beating out C++ and it can be natively compiled, too. If you need distributed components, you have one choice and one non-choice: Java or ActiveXcrement. Need I say more? I don't expect the form-building DOS hacks on this thread to grasp any of this.
Do you want to work with a hairball or a homogeneous environment: Java server code, Java client code, Java IDEs, Java APIs, Java documentation, Java HOW-TOs, Java training, Java Components, Java patterns, Java ubiquity. It's already the lingua franca of distributed computing. Because of it's extensible design, it's going to make C look like a blip on the information technology scene. |
