Like everything else, Java has it's place.  For deploying to the =20
masses, it's probably best to go off and develop something native for =20
each intended target platform.

However, Java becomes quite appealing for corporate apps that need to =20
run on multiple platforms.  It's been quite a while (~10 years) since =20
I did any Java development (except for my recent dabbling with Android =20
dev), but up to that time, we were developing in-house applications =20
that needed to run on multiple platforms (Win, Unix and Mac) and Java =20
saved tons of time.

Within reason, performace is good.  But then again, we developed a =20
very large app on Smalltalk for multiple target platforms and =20
performance bogged down so much as the app grew during intial =20
development, that the project was scrapped.  By comparison, Java was a =20
Veyron back then. :)

Cheers,
-Neil.



Quoting "M.L." <m@lkeng.net>:

> I wouldn't say "natively" I'd say "like crap"
> I've seen few Java applications that don't run at 1/100th the speed of
> their previous (non Java) version.
> Am I wrong? Are there good examples of large, complicated, Java
> applications that run just as well as a natively compiled version?
>
> --
> Martin K.



--=20
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist
.