[UFO Chicago] Java IDE

Nick Moffitt nick@zork.net
Mon, 7 Jan 2002 20:57:55 -0800

begin  Elliot Shank  quotation:
> Heh.  If you're going to start working in Java, you're going to have
> to start getting used to changing JVMs... you'll always be switching
> between several.

> If Java was designed to be portable, why is it so much easier to
> port C programs to different Unixes than it is to port Java programs
> to Java Runtime Environments on different Unixes? I've heard people
> complain they cannot get the Freenet distribution (an anonymous
> file-sharing and publishing architecture written in Java) to work on
> JRE X, so they are trying JRE's Y and Z instead to see if problems
> are less catastrophic there. If Freenet were a C program, it would
> have been picked up by all the Unix package collections by now, and
> would be just as easy to install as lynx or mutt. Since it's written
> in Java, it's a portability nightmare, and only a small inner circle
> has gotten it almost-working. Java's decoy claims of portability
> have in effect killed the Freenet, and dragged the Freenet
> architecture down to the same level of broken fantastic promises
> that Java makes. ``The mythical Freenet about which we have heard so
> much.''
> If Java itself is portable, then why isn't there a portable way to
> install and run a Java program without dealing with spaghetti
> .class-files, setting CLASSPATH, and referring to arcane modules
> contained within .jar files? Why do we have to use a Unix shell
> script to start a supposedly-portable Java program?

	01234567 <- The amazing* indent-o-meter! 
        ^	    (*: Indent-o-meter may not actually amaze.)