More precisely, "Does Aspect Oriented Programming (i.e. AOP) supercede Component Models?".  It's an interesting question, something we all would like to know before the AOP hype machine gets to full gear.  To answer it, let's get our definitions straight first.

Dumbing down the language by not providing more powerful expressions is a way of promoting to a wider audience. However, is it the only way of supporting communities?

It doesn't take much brains to build a virus. What takes brains is building software that other people want to buy.

"Humility: be generous in what you receive; be meticulous in what you provide." --John D. Mitchell

Why a technophilic Luddite would choose to write a blog

Jini must be one of the most misunderstood technologies out there today. In these Weblogs, I'll try to post a couple of brief essays from my experience using Jini in an enterprise application. This first essay talks about recovering from network-induced exceptions.

The Java collection class library has some fine qualities, and having a standardized set of collections is certainly far better than not having it. But the library also has a number of flaws that should be discussed and understood, so that they don't get perpetuated in future libraries. This article discusses two of the more irritating issues.

Having whacked the hornet's nest once, I take another swing, trying to clarify what I was trying to say originally. Is that a buzzing I hear?

SOAP, RMI, CORBA, RPC, Middleware, yadda, yadda, yadda. I'd rather use a socket.

The weakness of Design Patterns is that the mainline of code may be obscured. "Refactoring to Aspects" may prove to be a better alternative.

Common wisdom, especially in distributed computing, says that the right approach to all problems is to use a standard. This common wisdom has no basis in fact or history, and is curtailing innovation and rewarding bad behavior in our industry.

For Python programmers, I've got some suggestions on how to write a main() function that's easy to invoke in other contexts, e.g. from the interactive Python prompt when you feel like experimenting.

Five usability rules of thumb on how to design your API's.

Tim Bray has an interesting set of blogs that's keeping me on the edge. Tim is essentially saying that Java's immutable String class isn't suited for "heavyweight" text processing tasks. That's a big claim since there's just too many applications that require heavy text processing.

...Wherein we explore what makes a paper Top Notch, primarily by example.