Gerald, Microsoft's changes to the API have nothing to do with performance. Please post some pointers to backup your claim that writing "Windows only Java" offers superior performance. With pure Java you are always free to pick your favorite JVM or native code compiler that offers the best performance. The Microsoft API changes simply don't affect this.
You claim this, Microsoft claims otherwise. He said, she said.
An article I found with a quick search (I'm not going to commit any more time to documenting this):
bristol.com
By tying Java to Windows, cross-platform portability will be sacrificed in exchange for more versatility in accessing Windows functions and better performance for Java applications running on Windows platforms, Willis said. J/Direct is a logical step in Microsoft's ongoing efforts to make Windows the best platform for Java, he added.
Admitted by Sun:
But to this day, Java programmers are still faced with a dilemma programmers have always faced: They can tie their code to a specific system using less than "100 percent pure" Java, making their programs faster and more versatile, or they can write strictly to the Java APIs, making their programs portable but less efficient.
As JavaSoft defines more APIs and works at improving the performance of Java, that tradeoff will disappear, Paolini argued.
and
Paolini admits that much. But he says programmers should decide if they want to write for today's systems, which are predominantly Windows based, or the systems of the future which will be centered around the Internet. |
