How Microsoft adds COM to everything

I’ve been writing a retrospective on Microsoft and noticed an intriguing pattern.

When Microsoft was fighting the browser wars, it first of all developed its own web browser, and then added COM (ActiveX).

When Microsoft was countering Sun’s Java, it came up with its own implementation, Visual J++. Key differentiator: COM integration.

When Microsoft was responding to Adobe Flash, it came up with its own implementation, Silverlight, and then – you guessed.

The reason is that COM is the gateway to everything Windows; but it is a frustrating habit for those who want to live in a cross-platform world.

5 thoughts on “How Microsoft adds COM to everything”

  1. There is nothing stopping people from implementing them on other platforms (wine probably does a lot of them)

  2. There is nothing stopping people from implementing them on other platforms (wine probably does a lot of them)

    Not so, these are Microsoft products and only Microsoft can add features to them.

    Tim

  3. What kind of bullshit is that? Moonlight does whatever it wants, if it wants to say, have a internal implementation of the COM location API or call out to WINE, it can

Comments are closed.