There have been some intersting comments by Guy Steele on the ll1 maillist regarding design decisions in Java. Tidbits follow.
You know how local variables or arguments that are “captured” by an inner class need to be declared final? Well, it originally wasn’t going to be that way. We would have had “closures”:
On the subject of developer morale, I was just reminded by a friend of a joke he played on me while at University. A cruel, cruel joke.
Spotted the use of the splash task in the Hibernate build.xml today (via BPH). So of course I had to add it to Clover’s build file. You can see the results in this image:
I’ve been tweaking quite a few Ant build files at work in the last couple of weeks. Firstly, thank crap for IDEA and its Ant completion mode (Eclipse has a similar mode). Also, being able to comment out a whole XML block with Ctrl-Shift-/ is nice, too. Secondly, there is a certain amount of noise in an Ant XML [...]
We have just released (beta) Eclipse and NetBeans plugins for Clover, allowing you to instrument your code and view coverage results all from with the those Java IDEs.
For the longest time, I’ve been happily deluding myself that the ++ operator is atomic in Java. I tried never to give it much thought because I wanted it to be atomic. But those blissful days are over.
Complexity is conserved by abstractions.
Could a programming language last “forever”? What about a thousand years? How long do you think Java will last?
Is that Tomcat’s hind leg… or something else. You decided. (from here)
(image)
