Java is supposed to be platform independent
If I had to pick one issue in this book that I think is most controversial, it would be platform-dependent applications. From what I read on the newsgroups and in the press, I think that many programmers agree with me. As you'll see in Part III, I myself am quite torn about the whole idea. sewa-plasma
Much of this concern is misguided, however. If Java is to fulfill its promise as a full-powered environment for developing applications, then it cannot be hobbled by requirements that are intended for applets on Web pages. Only by taking advantage of undocumented packages and the native API can Java programmers level the playing field with their C and C++ counterparts and produce commercial-quality applications.
The advent of Java-based network computers only extends the problem. On a network computer, anything you want to do must be done in Java. You cannot drop out to a native method in C. Therefore it is even more important to have full access to all the capabilities of Java. sewa-plasma
What went wrong? What happened to the dream of applets moving transparently and easily between platforms? The answer is that Java succeeded. In fact, it succeeded wildly, much faster and far beyond the expectations of its designers. What was a simple language for consumer electronics has become the most rapidly adopted programming language in history. It is being used for applets on Web pages, for database front ends, for numerical analysis, for multi-player networked games, and for much, much more. It is no wonder that many of these programmers need capabilities and knowledge that were not originally planned for Java.sewa-plasma