What has Java to do with bloatware?

Everything; go back to Java 1.2, then with each new release from Sun look at the size of (a) the JDK install and (b) the JRE install. We'll ignore the obese J2EE to save you wasting your time finding out how big that puppy is.

Consider MicroSloth, on the other hand: Each new version of WinDoze is
that much bigger and slower than the previous one, and every single one
of them has been so unstable that even an operating system written, in
part, by amateurs in their spare time is an improvement in terms of both
efficiency and stability.

You don't do much heavy Java programming, do you? It shows. Sun's implementations of both JDK and J2EE fit that loose description too. And guess what, non-Sun implementations (some amateur, some commercial) of those work way better too. I know I'd rather run J9 where ever I can, vs. Sun's own JVM.

Java6 does not run as swiftly as Java 1.2 on *same* hardware - you need to beef up your hardware for Java, too.

Or haven't you noticed that a typical WinDoze
box requires enough processing power, memory, and hard disk space to
support a small timeshare system under any other operating system?

Oh and I run Debian and Windows XP in VMWare images (OS specific versions of our software and a set of development tools on each - that's about it) - funny how my (minimal install) Debian image started at 8GB is now running at 12GB and my Windows XP image (accepting all the defaults) that also started at 8GB is now running at, oh, wait, 8GB.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].