Disadvantages with Java
In the quest for portability Java deliberately left out access to system-specific things. You can't directly call Windows APIs or COM or DDE or 3rd party DLLs.
This is true in general, but Sun and other third parties are striving to provide JNI or similar interfaces to allow such access... take JavaSound: there's a Java abstraction on top of the native OS hardware communication, but you can still do practically everything you can with a C/C++ application (but in a much more elegant way). Same with the addition of some classes in the Image I/O which make use of graphics cards and their hardware acceleration.
Another new example of this (which I only found out about a couple of weeks ago) is the addition of the java.lang.Process and ProcessBuilder classes which enable you to start and control processes directly in the OS (outside the JVM)... this is incredibly useful, and prior to J2SE 5.0 would have most likely required a native driver program.
Link-I
Link-II
This is true in general, but Sun and other third parties are striving to provide JNI or similar interfaces to allow such access... take JavaSound: there's a Java abstraction on top of the native OS hardware communication, but you can still do practically everything you can with a C/C++ application (but in a much more elegant way). Same with the addition of some classes in the Image I/O which make use of graphics cards and their hardware acceleration.
Another new example of this (which I only found out about a couple of weeks ago) is the addition of the java.lang.Process and ProcessBuilder classes which enable you to start and control processes directly in the OS (outside the JVM)... this is incredibly useful, and prior to J2SE 5.0 would have most likely required a native driver program.
Link-I
Link-II
posted by Vishnu at Tuesday, May 23, 2006
0 Comments:
Post a Comment
<< Home