Bruce Eckel, author of Thinking in Java has a controversial blog entry about generic types in Java 1.5.
I believe that Bruce has largely missed the point of Java's generics, and that the "latent typing" ideas he discusses would take Java in a very unJava-like direction. His post turns into something of a rant, but the crux of it seems to be this:
I feel lied to (by the term generic)
Basically, Bruce had heard about generics in Java 1.5, but had not yet read about them. The use of the word "generic" gave him a very mistaken idea about what this language feature actually entails. And then when he actually sat down to study generics in Java he was sorely disappointed.
I don't want to debate Bruce's other points here. I am curious, however, whether anyone shares Bruce's concern that the term "generic" when applied to Java's parmeterized types, promises something beyond what Java delivers. I haven't read Bruce's books, but he's presumably a pretty smart guy. If he's gotten this confused by the use of the word, I wonder whether others share his confusion. If the term "generic" is confusing, I'll want to avoid it in the next edition of Java in a Nutshell, or at least include a footnote about the potential confusion.
If you're familiar with generics in Java 1.5, and have used a similar facility in another language, your comments are encouraged!



