10.20.07
Quick Updates on Linspire and SCO — Two Companies That Won’t Recover
Thinking differently, but making the same mistakes
While Linspire didn’t intend to harm Linux, it is likely to end up just like SCO, especially after its Linux FUD and short-lived relationship with Microsoft. With lost appeal, lost direction, and lost staff, there is little left to see there.
Here is a new interview with Linspire’s new CEO, which doesn’t mention the deal with Microsoft. Larry Kettler talks only about the product and the privately-held company in reply to questions. Linspire is probably lucky enough to have a wealthy founder, so it might stay around for a while. On the contrary, SCO is running out of money. It is finding out the hard way that litigation doesn’t pay off. Au contraire — it costs plenty.
SCO vs. Linux: Costly German lawyers
The never ending story surrounding SCO’s litigation over alleged copyright infringements contained in Linux as well as the copyrights to Unix has taken yet another twist: The SCO Group, currently subject to proceedings under Chapter 11, is causing a stir as details in relation to their payment obligations emerge.
That is the cost of going against the spirit of the technology-savvy community. Xandros and Novell are yet to face the wrath of the customer at its worst form. Without the supplier (programmer), these companies are worthless. They have limited control.
Highlight: Novell was the first to acknowledge that Microsoft FUD tactics had substance. Novell then used anti-Linux FUD to market itself. 
Highlight: Xandros let Microsoft make patent claims and brag about (paid-for) OOXML support. 
Highlight: Linspire's CEO not only fell into Microsoft arms, but he also assisted the company's attack on GNU/Linux. 
Highlight: Microsoft craves pseudo (proprietary) standards and gets its way using proxies and influence which it buys. 
Highlight: The invasion into the open source world is intended to leave Linux companies neglected, due to financial incentives from Microsoft. 
Analysis: Xen, an open source hypervisor, possibly fell victim to Microsoft's aggressive (and stealthy) acquisition-by-proxy strategy.