Disclosure: I'm a Java developer, but I do enterprise server-side development, not web development.
Having said that, I agree with Apple's decision to deprecate Java, and I'm not foaming at the mouth like some Java devs are. Apple has been slowly backing out of their commitment to Java made in 2000, and this is the continuation of that long process. Losing the Java devs who buy Mac Pros and MacBook Pros would have been devastating to Apple in 2000, now it's a manageable loss. Hopefully, Apple is putting lots of pressure on Oracle to provide a full Java implementation on Mac. They've certainly laid the groundwork for this by re-working their Java file/directory structure from a byzantine mess of files installed all over the filesystem with only one Java runtime allowed per version, to localizing it to a specific directory in which multiple Java runtimes can be installed for the same version. Apple is putting a significant effort into bowing out of its Java commitment gracefully.
Also, I feel it's Oracle's responsibility to provide a full Java runtime for OS X, including Swing/GUI. Oracle acquired Sun's commitments when they acquired the company, and they absolutely should not back out, especially having committed to Java FX 2.0.
Also, the Apple Java devs are wonderful, committed and very helpful people people. They take a lot of abuse on the java-dev mailing list, and are bound by really tight NDAs that prevent them from commenting on any of the Apple Java policy decisions, but are extremely helpful for specific technical questions, answering emails on the weekends. I make special mention of Mike Swingler.
I'm concerned about the potential lack of Java on Mac from anyone, and it will make me consider my choice of platform. I'm otherwise extremely satisfied with the Mac experience, and would be extremely reluctant to switch to Linux or Windows (which makes my skin crawl just thinking about it).
Originally Posted by technohermit
This Trojan runs perfectly fine, it's not exploiting a hole in Java, nor a hole in OS X.
The decision to remove Java from OS X installs means Apple thinks their popularity will entice Oracle to keep Java up to date on their own. It also means OS X updates are finally going to get smaller to download. Perhaps we can have updates more frequently, rather than wait for the updates to come through Apple we can download them ourselves separately.
It may work, it may not. Maybe Oracle won't put in the resources necessary to maintain feature parity with Windows and Linux. Maybe they will who knows? I know there were times I wish my nVidia updates would have come out prior to an OS update. Without Apple's input and help in maintaining the code the updates may get fewer and farther between, or not be coded as well.
There's something to having the hardware manufacturer writing the software for their platform, is there not?