Apparently PHP, Ruby et al have kicked Java’s butt so hard, it’s having a problem sitting down. JSR 270 which handles Mustang suggest a process for removing features from the Java language. As in “less is every one else’s killer feature”.
The multi-step removal process means we won’t see much improvement any time soon, and there are more additions than removals. But still, it’s a nice idea to play with.
The current list suggests removing java.sound.midi on account that no one is using it. Here’s a few more suggestions:
- Remove Derby from the same release you intend to add it to.
- Identify the one person using Crimson, if you can’t, save us from JAXP.
- Move Java 3D to the “Eye Candy for Demos” edition of the JDK.
- Until Java ships in a browser, java.applet can go.
- javax.naming. Let’s teach people how to write better code.
- CORBA. Ain’t happening on the desktop. Let it go.
And while we’re at it, if java.awt and java.swing disappeared and all of a sudden we got SWT, you might even put a smile on my face.
What would you suggest for the Java diet?
Hat tip to Alex, photo by malias.