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.

VN:F [1.9.9_1125]
Rate this post
Rating: 0.0/10 (0 votes cast)

Related posts:

  1. Zend PHP Framework adds support for Adobe Flex, AMF
  2. Native code interop in Adobe AIR vs Microsoft Silverlight
  3. Speeding page load with dynamic JavaScript
  4. Microsoft pledges commitment to Silverlight – but is it enough?
  5. Counting primes in Google Chrome

5 comments to How Microsoft adds COM to everything

  • asf

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

  • tim

    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

  • asf

    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

  • tim

    Sure, Moonlight can do that. Moonlight is not Silverlight.

    Tim

  • asf

    And how do you run Silverlight on *NIX? MS is even helping them

Leave a Reply

 

 

 

You can use these HTML tags

<a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>