To me, one of the most enjoyable parts of JavaOne is hanging out in the audience in Hall E-135 (traditional home of the Desktop track) and chatting face-to-face with developers between presentations. Kirill Grouchnikov (of Substance look-and-feel fame) always asks us insightful and often difficult questions.
In the early days of Swing we spent many lunches arguing over the best way to do GUI layout.
A little more than 50 years ago, a team of brilliant engineers and mathematicians set out in the confines of an old battery factory in Philadelphia to build the world's first supercomputer, the UNIVAC LARC. My mother (Mary Cush, at the time) was on that team.
For some time I've been peddling this theory that one of the greatest barriers to Swing adoption is our monolithic API documentation (javadoc).
At JavaOne '97, we kicked off project Swing and as we raised the toolkit scaffolding in the crazy months that followed, we released frequent snapshots of the bits to get our developer base (or at least a hardy core) in on the action. Feedback, both positive and 'constructive', was relentless, and the API improved steadily because of it.
True confession: I love my Mozilla mail filter panel.(For non-mozilla users,
this is the ever-present textfield that filters my message
headers as I type, making it so very easy to find messages quickly).
I'm also wildly fond of browser smart-fields that use auto-complete to
recall my userid/password at the umpteen different websites where
my memory always shorts.
Recently my 15-year-old cassette walkman that I use for running
finally keeled, leaving me with no choice but to upgrade to an iPod.
Powered by 802.11 and my viao with its duck-taped powercord to prevent
hibernation loops, I'm basking in a balmy California midnight outside
on my deck, coding away, fighting off an onslaught of bugs.
Now you'd think that since I've worked on the JDK for many years that
I'm referring to knats in the software.
Rewinding back to JavaOne2000, a few of us on the Swing team put
together a session called "WebAwareWare" (forgive us, this predated
"Web Services" as a household name). In the session we
built a rich client version of a little web application called "Blogger",
written by a couple guys at Pyra Software.