🚀 go-pugleaf

    I think you very well described the situation... I'd like to add
something: the fact Java compilers generates only byte-code (I mean .class
files) allow you to distribute your app on many OS. At this time, your apps
can be executed under MacOS, RiscOS, Linux, Solaris, AIX, Window$, BeOS...
This is a very good way to make your app being well known by a lot of
different users.
    But Java world is not always bright... First at all, we often encounter
JVM (or default classes) bugs which let you think your app is bugged. Next,
because Java can run on so many platforms, GUI can act weird under Linux
although it was perfect under Linux. This happens mainly with AWT
components. At last, Threads are not handled the same way. For example,
Threads are native under Win32. This means if you have three threads they
are executed simultanely (almost). But under, Linux, the JVM use green
threads: a thread exeute and when it has finished, another thread can
execute (when I say execute, I mean executing one method). And I forgot the
paths problems. Win32 uses \ as path separator, Linux /, MacOS :, etc...
Take care of it !

                                            Romain Guy