On Wed, Jan 02, 2002 at 04:52:50PM -0800, Ian Clarke wrote: > On Wed, Jan 02, 2002 at 08:34:09PM +0100, Oskar Sandberg wrote: <> > > You can't possibly have every piece of software referenced in a path > > line, and that isn't what people are doing. Instead they are using shell > > scripts that set the classpath before executing with every program - > > resulting in a Windows like situation where every program is distributed > > with all it's dependancies (making the effort toward unique naming > > completely pointless). > > I don't think that we should be worrying about the woes of Java software > distribution, we should be worrying about what makes life easiest for us > and our users. Adding a directory to a classpath and the removing it > afterwards does not preclude use of other pre-installed libraries. I > agree that it would be a better world if java software was always > spliced into a global tree on a machine during installation, but we > don't live in that world, and if we pretend that we do, it will be a > world of pain for all.
The world of java on the client does not exist (partially do to stuff like this). If Fred were ever successful, it would most likely be the first popular client side java application - I don't think that "everybody else is doing it" is responsible reasoning here. > > It would seem to me that being able to locate all the existing classes > > would make upgrading a hell of lot easier (say there is a bug in a > > crypto class used by twenty programs - good luck if every program dumped > > it in the jar where nobody can see it). > > Yes, all very well if there was a pre-existing cross-platform standard > practice to place all Java class files in a well known and unified tree, > but there isn't. So we make one. <> -- Oskar Sandberg oskar at freenetproject.org _______________________________________________ Devl mailing list Devl at freenetproject.org http://lists.freenetproject.org/mailman/listinfo/devl
