Wednesday 1 October 2008

Competing with open source software

Not long ago, there was a book published by Stanford on how to compete with open source software without being open source yourself. Apparently one "tip" was to "embrace and extend" open standards (which is a Microsoft phrase). The upshot of that practice is that your product can be used in place of any open source alternative, but once people start using your "extended" features, others need to start using your product too. And since there is no alternative for those features, you eventually take over the market, edging out the competition by degrees.

The main problem I have with this approach is that it theoretically works even if the replacement product is worse than the open source ones. All it needs is one person somewhere to start using the new features, then someone else has to switch to the other product for compatibility, or at least keep a copy at hand. Before long, it's too annoying to use the open source product as well as the closed one, and your customers are annoyed into using your product exclusively. That's not clever sales or even good programming. It's an infection.

Mokalus of Borg

PS - So there you have it. Closed source software is a disease.
PPS - It's worst when it's designed to work that way.

No comments: