Java VM--virtually meaningless?
zdnet.com
It turns out--no surprise--that you are better off optimizing your
operating system for Java, rather than running a Java VM on your
existing operating system. Essentially, the JVM left out a few things
that are needed for NC computing, such as central server management
and allowing hardware vendors to write different device drivers. And
the performance needed tuning, too. Why not just implement those on
the VM? Well, the bottom line is that the fewer layers between your
application and the hardware, the faster the application runs.
It has taken us two years since the NC rollout to discover
this?
Apparently, for NCs, which are now basically dead in the water, to
succeed, they need what is essentially a native implementation of the
Java VM. And it needs to be common across different vendors' NCs.
"This gives specific guidance to developers. They want one platform
for network computers," said Janpieter Scheerder of Sun. So it seems
that the VM as a common platform wasn't quite enough.
...
So the Java mo rolls onward, and the environment becomes more
robust and ready for IT prime time. All well and good. But write once,
run anywhere? Depends on the application. Depends on the operating
system. Depends on the platform. What else is new?
********************
Imagine, developers want one platform for network computers. You
would think the Unix experience would have been enough but I guess it
took Sun, IBM, etc. another two years of wasted efforts to figure out
what developers really want. |
