Alex Blewitt wrote:
> Actually, does that need to be the case? The reason for Java's
> bloatware is that There Is One Library.
Having worked on the J2SE API Specification myself (for IBM) and also
observing exactly how JSR teams operate (both on J2SE and J2EE
(WebSphere)), I have always attributed this to Java's offensive type
system, inherent strictness (i.e. laboriousness to emulate laziness) and
general failures of abstraction.
To pick a trivial example, exactly why *do* we have java.io.InputStream
and java.util.Iterator anyway? How often in the core API is the same
thing rewritten over and over with a different euphemism attached? I
would say a great many times.
<plug>
Hence, I have a Scala/Haskell-inspired attempt at making Java less
annoying (but still very annoying)
http://jatheism.net/</plug>
That's my two cents :)
Tony Morris
http://tmorris.net/
