Those of you who've seen me speak on Java 7 at various conferences have heard me lament
(in a small way) the fact that Sun decided last year (Dec 2008) to forgo the idea
of including closures in the Java language. Imagine my surprise, then, to check my
Twitter feed and discover that, to everyone's surprise, closures are
back in as a consideration for the Java7 release.

Several thoughts come to mind:

Read more ...

Those of you who've seen me speak on Java 7 at various conferences have heard me lament
(in a small way) the fact that Sun decided last year (Dec 2008) to forgo the idea
of including closures in the Java language. Imagine my surprise, then, to check my
Twitter feed and discover that, to everyone's surprise, closures are
back in as a consideration for the Java7 release.

Several thoughts come to mind:

Read more ...

Those of you who've seen me speak on Java 7 at various conferences have heard me lament
(in a small way) the fact that Sun decided last year (Dec 2008) to forgo the idea
of including closures in the Java language. Imagine my surprise, then, to check my
Twitter feed and discover that, to everyone's surprise, closures are
back in as a consideration for the Java7 release.

Several thoughts come to mind:

Read more ...

Phil Haack wrote a
thoughtful, insightful and absolutely correct response to my
earlier blog post. But he's still missing the point.

Read more ...

Phil Haack wrote a
thoughtful, insightful and absolutely correct response to my
earlier blog post. But he's still missing the point.

Read more ...

Phil Haack wrote a
thoughtful, insightful and absolutely correct response to my
earlier blog post. But he's still missing the point.

Read more ...

The above quote was tossed off by Billy Hollis at the patterns&practices Summit
this week in Redmond. I passed the quote out to the Twitter masses, along with my
+1, and predictably, the comments started coming in shortly thereafter. Rather than
limit the thoughts to the 120 or so characters that Twitter limits us to, I thought
this subject deserved some greater expansion.

But before I do, let me try (badly) to paraphrase the lightning talk that Billy gave
here, which sets context for the discussion:

Read more ...

The above quote was tossed off by Billy Hollis at the patterns&practices Summit
this week in Redmond. I passed the quote out to the Twitter masses, along with my
+1, and predictably, the comments started coming in shortly thereafter. Rather than
limit the thoughts to the 120 or so characters that Twitter limits us to, I thought
this subject deserved some greater expansion.

But before I do, let me try (badly) to paraphrase the lightning talk that Billy gave
here, which sets context for the discussion:

Read more ...

The above quote was tossed off by Billy Hollis at the patterns&practices Summit
this week in Redmond. I passed the quote out to the Twitter masses, along with my
+1, and predictably, the comments started coming in shortly thereafter. Rather than
limit the thoughts to the 120 or so characters that Twitter limits us to, I thought
this subject deserved some greater expansion.

But before I do, let me try (badly) to paraphrase the lightning talk that Billy gave
here, which sets context for the discussion:

Read more ...

Recently I've had the pleasure to make the acquaintance of Walter
Bright, one of the heavyweights of compiler construction, and the creator of the
D language (among other things), and he's been great in giving me some hand-holding
on some compiler-related topics and ideas.

Read more ...

Recently I've had the pleasure to make the acquaintance of Walter
Bright, one of the heavyweights of compiler construction, and the creator of the
D language (among other things), and he's been great in giving me some hand-holding
on some compiler-related topics and ideas.

Read more ...

Recently I've had the pleasure to make the acquaintance of Walter
Bright, one of the heavyweights of compiler construction, and the creator of the
D language (among other things), and he's been great in giving me some hand-holding
on some compiler-related topics and ideas.

Read more ...

Recently, an email crossed my Inbox from a friend who was concerned about some questionable
practices involving my content (as well as a few others'); apparently, I have been
listed as an "author" for SysCon, I have a "domain" with them,
and that I've been writing for them since 10 January, 2003, including two articles,
"Effective Enterprise Java" and "Java/.NET Interoperability".

Read more ...

Recently, an email crossed my Inbox from a friend who was concerned about some questionable
practices involving my content (as well as a few others'); apparently, I have been
listed as an "author" for SysCon, I have a "domain" with them,
and that I've been writing for them since 10 January, 2003, including two articles,
"Effective Enterprise Java" and "Java/.NET Interoperability".

Read more ...

Recently, an email crossed my Inbox from a friend who was concerned about some questionable
practices involving my content (as well as a few others'); apparently, I have been
listed as an "author" for SysCon, I have a "domain" with them,
and that I've been writing for them since 10 January, 2003, including two articles,
"Effective Enterprise Java" and "Java/.NET Interoperability".

Read more ...