On Plug-ins and Extensible Architectures

gManZboy writes "Developers who want a flexible, configurable, IDE have long preferred plug-in architectures such as Eclipse over what they might view as the bloated, monolithic alternatives. Ever wondered how it all works? Well, ACM Queue just posted an article by someone who has worked on Eclipse since its inception, Dorian Birsan. He gives a great explanation of the Eclipse architecture as well as a thorough analysis of things to watch out for when developing or working with pure plug-in architectures."

Comments

Inversion of Control

[irritating environme]

To all you pattern zealots out there, this is called Inversion of Control. Typical crappy pattern name. Service patterns are among the most common used. Why? Because they are well-named. Who the hell came up with Inversion of Control? Pointless terminology. Plug-In Architecture is far more descriptive, understandable. Although you pattern guys don't get to sound like snotty professors when you say it. It's far too...practical