Red Hat’s limited greed

I guess the theme du jour is the motivating power of greed. It was going to be du jour but I didn’t get time to post before leaving.

Long overdue, I’m busy working on my presentation for the conference next Monday in Copenhagen. In trying to explain openness to fellow academics, I’m interested in the “open” strategies that really aren’t — or, perhaps to be more fair, are only partly open.

Red Hat is one of the examples that comes to mind, since their per-CPU license fee looks a lot like Microsoft’s. This is oft-remarked among open source users occasionally gets noticed, although apparently not that often in print.

One example where it was is when Sun CO Jonathan Schwartz referred to Red Hat as “"a proprietary Linux distribution.” He’s not the most objective commentator, but Ian Murdock (the Ian of Debian Linux) agreed. And perhaps the comment was provoked by (never bashful) Red Hat CTO Michael Tiemann criticizing “Java apartheid” — which would be fighting words around here.

Criticism from the community side was published in January by Ubuntu Project founder Mark Shuttleworth, who wrote:

As free software becomes more successful and more pervasive there will be an increasing desire on the part of companies to make it more proprietary. We’ve already seen that with Red Hat and Novell, which essentially offer free software on proprietary terms - their “really free” editions are not certified, carry no support and receive no systematic security patching. In other words - they’re beta or test versions. If you want the best that free software can deliver, a rock solid, widely certified, secure platform, from either of those companies then you have to pay, and you pay the same price whether you are Goldman Sachs or a startup in Rio de Janeiro.

Of course, firms have to make a profit and I’m the first to praise such motivations. I just think some of the claims of openness in the industry are disingenuous — in a few cases, it's no more than a marketing slogan (like the late lamented “OpenVMS”).

BTW, if you want to know what Red Hat’s business model is, Matt Asay spells it out, based on a Red Hat presentation. To my mind, he draws only a nuanced distinction to the proprietary source model:

The model requires constant innovation. This is not good if you're trying to milk a product for monopoly rents ("Monopoly" here referring to the limited monopolies afforded through copyrights and patents).

My problem with this claim of Red Hat innovation is that any software company finds it easy to innovate when it’s young. The key is whether it can continue to provide incremental improvements, valued by customers, long after the core features have been implemented.

In my first job out of college, back in 1979 or 1980, my supervisor (our office had only one “boss”) Glenn D. Johnson said something to the effect that all operating systems stop at 8. With each major release, the cost of upward compatibility becomes worse and worse until eventually the delay between releases becomes infinite. He was thinking of IBM’s MVS (later abandoned), but it also matches my experience. Mac OS ended with 9.2.2, but it skipped directly from 1.x to 4.x. Also, Apple renumbered 7.7 to 8.0 to trigger the Copland clause (and kill cloners). So that means Mac OS had 6 or 7 major releases, not 9.

Technorati Tags: business models, Linux, Red Hat