Why Writing Dumb Code is a Smart Idea
A new interview I did with Sun technology evangelist Brian Goetz,
"Writing Better Code:
A Conversation With Sun Microsystems Technology Evangelist Brian Goetz"
explores several areas of his considerable expertise. He addresses
concurrency issues; the problems Java developers have in identifying
performance problems (think architecture, not coding); the importance
of writing clean "dumb code" and trusting the JVM; the overuse of XML;
the problems C programmers have in learning Java programming; the
distinctive improvements in J2SE 5.0 and Java SE 6; the myth of
expensive object allocation; and the as yet unsung virtues of JSR 223 --
He clearly thinks that Java developers, in some
areas at least, have got it wrong. Anyone think he's got it wrong?