10 Reasons We Need Java 3
An anonymous reader writes "This article on O'Reilly Network (written by one of the most active Java book writers ever, Elliotte Rusty Harold) has some interesting points about the need for a new 'cleaned up' Java version, made to incorporate the advances in the last 7 years of its life and without the requirement to keep compatibility with old versions."
...is to know what to use to make it work on all of your target platforms...and wasn't this supposed to be one of Java's strong points? So, actually, a fresh start might not be that bad at all.
10. Get rid of deprecated methods - don't be an arse, ruins past compatability with no benefits.
9. . Fix incorrect naming conventions - Jesus, Get OVER it!
8. Eliminate primitive data types - oh yeah, please let me do x = new Int(1) + new Int(3);
7. Eliminate primitive data types - oh, ok then
6.
OK, bored now...
but, really,
No single topic is as confusing to new users as the class path. I get almost daily e-mail from novice readers asking me to explain the "Exception in thread 'main' java.lang.NoClassDefFoundError: HelloWorld" error messages they keep seeing.
Well, tell them to get fucked and go and read the Java tutorial then! You don't even need classpath from Java 1.2 onwards. Jesus, let's redo a language because first-time users can't get Hello World to work!
This is a really wank article - I like the conclusion..
Java needs fixing, I really don't know how or why, so lets discuss it. Arse. and Arse again.