🚀 go-pugleaf

Richard Wilkman <rwilkman@inprise.com> wrote:

>Hakan:

>There are no "methods in JBuilder" to avoid.  The rules for
>portability in Java are simple.  Don't reference Native code.  That's
>all that John is talking about.  If you've written JNI code for one
>platform, you can't just take it to another.

>There are still portions of Java 1.1 that are not implemented on all
>platforms (most often because there is no implementation on the local
>platform to leverage).  That's stuff you will pick up as you use a
>particular platform version of the JDK.

>-Rich

The problem is when you want to create applications which communicate
with hardware, and this is a common type of application:

For example I have a school project in java that is perhaps not
feasible: a video+audio capture application from a camera that sends
images in realtime on tcp/ip needs to read parallel or serial port and
record wav from a sound card: It can be done but only whith APIs that
are platform-specifics.

First the project had to be written in portable pure java, but I
realize that it will not be so why would I continue wanting to use
java for such a program ?