Much has been said in the last 24 hours about Microsoft's newest interoperability/openness pledge. I won't rehash all of it, but it's interesting to think about how the software behemoth's new strategy will affect open source.
First, Ballmer and company said that they would not sue open source developers for non-commercial development based on protocols that Microsoft has released. However, they also very specifically pointed out that they were not extending the same covenant to commercial developers. So, as News.com blogger and Alfresco Software VP Matt Asay puts it:
It's an imperfect commitment on Microsoft's part, almost undoubtedly driven by the need to placate European Commission regulators and to preemptively allay U.S. antitrust fears as a Yahoo deal nears.
He says open sourcers should "applaud even the baby steps" and then "push for more." His suggestion:
[O]ne thing that Microsoft could do is extend its Open Specification Promise to the API and protocol information it's opening up, rather than demanding license fees for these.https://o1.qnsr.com/log/p.gif?;n=203;c=204663295;s=11915;x=7936;f=201904081034270;u=j;z=TIMESTAMP;a=20410779;e=i
As New York Times writer Steve Lohr points out, the move is an indication that Microsoft understands the market is demanding more transparency and "a seamless flow of documents, data and programming code among desktop PCs and the Internet."