Comments on: Java Upgrade Hammer

By: Golly

Golly — Thu, 20 Dec 2007 22:01:20 +0000

@Matt: If you have “Integer i” and “Double b” both “Number n= i” and “Number n= d” works in java. It should be the same with generics. If you’re worried about accidentally stuffing a Double into a List of Integers like you say, then use a List of Integers rather than a List of Numbers.

By: praveen

praveen — Wed, 19 Dec 2007 08:54:14 +0000

We have moved to Java 5 & no problems & have seen quite improvement in performance. Before generics this code was more readable List/*Integer*/= new …., now with Generics it can be List, If you don’t like (& want it to be like C#) one don;t use it, After all it’s not mandatory to use generics.

This romour might become true http://www.macrumors.com/2007/12/18/apple-seeds-mac-os-x-10-5-2-and-java-se-6-preview-8-for-leopard/

With Groovy/JRuby I don;t why people are so passionate about introducing closures in JDK7. JDK should be left as it is (as for as language features are concerned)

By: Matt

Matt — Tue, 18 Dec 2007 22:44:42 +0000

@Golly: Well, there’s pitfalls if you say that List(Integer) is a subtype of List(Number), what with all that fancy “Liskov substitution principle” stuff. Personally, I’d like my compiler to prevent me from accidentally stuffing a Double into a List of Integers rather than have it die at runtime.

By: Golly

Golly — Tue, 18 Dec 2007 22:09:11 +0000

Oops, greater than/less than symbols didnt work.
“List is not a List” –> “List(Integer) is not a List(Number)”

By: Golly

Golly — Tue, 18 Dec 2007 22:06:53 +0000

Java’s generics implementation is absolutely retarded. It completely breaks polymorphism (eg List is not a List). I’d still rather have it than not though.

Closures would be an excellent addition. Why do java people hate change to java so much? Java needs a LOT of change imo. There are lots of small things you could add to the syntax without breaking anything, and still maintaining all of java’s design goals that would greatly simplify the amount of code we write each day, the readability and also allow us to focus more on the actual business logic.

By: Michael

Michael — Tue, 18 Dec 2007 21:12:40 +0000

Is the new goatee guy Mr. Easter? If so, then I feel sorry for Mike…that’s a big hammer.

By: Neil Weber

Neil Weber — Tue, 18 Dec 2007 21:12:24 +0000

Having upgraded to Java 5 and then to Java 6 and encountering no problems, I don’t get it.

By: Jorge Diaz Tambley

Jorge Diaz Tambley — Tue, 18 Dec 2007 18:31:55 +0000

This picture is worth a million words

By: Smitty

Smitty — Tue, 18 Dec 2007 17:11:30 +0000

Geez, could you be a little less accurate . It burns, it burns….

We’re currently in a holding pattern with JDK 1.4.2 using WebSphere 6.0. Nobody in our organization wants to touch WebSphere 6.1 and JDK 1.5. Of course, eventually we’ll have to bite the bullet and move forward. I’ll be keeping one eye open for the big o’l hammer….

By: Alex Miler

Alex Miler — Tue, 18 Dec 2007 12:55:49 +0000

rotfl…great stuff