I really would like some examples of actual CURRENT use of Java based applications on the web. I can't seem to locate one that is not better or at least equally suited to run natively on my Mac.
http://variations2.indiana.edu/
I'd link to one I worked on specifically but it had to be canned because it relied on QT4J which Apple no longer supports in any meaningful context and will die off once the state of Java and Quicktime have progressed to the point where they're completely incompatible.
So find me an academic-grade music search and annotation application that
1. runs natively on your mac
2. runs natively on Windows
Why is this app written in Java? Because it is research-driven, thus its development was grant-funded, and you're never going to get a grant to fund development for an application if one of the stipulations is that it must be ported from one platform to another.
Granted, fewer applets are seeing the light of day with the advent of proprietary frameworks like Flash and Silverlight. While you want to restrict the conversation to applets, my point was much broader. This particular example is demonstrative of how Apple treats Java in general. There are a great many more desktop applications that are Java based and even more back-end apps use Java.
Probably the absolute most useful single tool I have in my day-to-day work life is Eclipse which is completely Java based. You know why a significant number of useful Eclipse plugins won't work on a Mac? Because Apple refuses to fix threading issues in Java. Not to mention, every UI event runs through a single thread, this bottlenecks the bejeezus out of Java apps running on a mac. It doesn't have to be that way. Doesn't work that way in *nix or Win JVMs. Oddly enough, Sun writes those JVMs...
Further, with the advent of SWT you are probably unaware of the number of applications out there that are Java based or utilize Java components. Regardless of the validity of your contention that *you* don't see Java in *your* world, Java is an integral tool in many environments. To unilaterally declare that Java should die is ignorant hyperbole. Apple ignores Java to its own detriment--especially given the 180 degree turn this shows from Apple's emphatic embrace of Java early in OS X. Corporate, government, and academic environments see this kind of arbitrary behavior from Apple and it confirms in their mind that this is a non-serious work platorm geared to diletantes and naifs.