As a reminder, as part of its many OOXML abuses, Microsoft paid companies to 'support' OOXML

Summary: The similarities between the effect of adding UEFI code and adding OOXML code to Free software

IN 40 comments or so I have been discussing UEFI with the developer of Shim, whose latest work one can read about in:

1. Shimming your way to Linux on Windows 8 PCs

   So, while Garrett's shim will soon be bring many more varieties of Linux to many more Windows 8 PCs, UEFI Secure Boot will remain a significant worry for anyone wanting to run Linux or other alternative operating systems on Windows 8 PCs.





2. HP Pavilion dm1-4310: SSD installation, and fun with EFI Boot

   Next I went to the other extreme, disabled Legacy Boot and enabled Secure Boot. In this configuration, the Live USB media for Linux Mint and openSuSE wouldn't even try to boot as they don't have EFI bootloaders included. Fedora 18 Beta would try, but failed — the necessary security certification is not yet included on the 18 Beta distribution. But Ubuntu 12.10 booted with absolutely no problem. Hooray!

UEFI was designed with lock-down -- not just "security" -- in mind. It's like TPM. Thus, Microsoft hoped to embrace the darn thing, making it harder to boot Linux. It doesn't take a wild theory to deduce this. We saw the same things around 2007, as I explained in comments alluding to hundreds of posts I had written in 2006-2008. Antitrust is bound to be hurt when the anticompetitive is embraced by that who is being hurt.

Speaking of which, check out what Simon Phipps says about Freiburg:

We recently saw the news that the German city of Freiburg had decided to end its open source migration and instead switch to using Microsoft products again. The rationale provided seemed curious to me - after all, at the same time the German city of Munich announced total savings amounting to €10 million from its own successful and ongoing migration.

What seemed odd was there was no account of how they changed course to make the migration succeed. Munich learned lessons from early challenges and updated its strategy in order to succeed. But not Freiburg.

From what I could see, instead of ditching the old versions of MS Office and OpenOffice.org they'd started with and installing up-to-date LibreOffice using expert in-house help, they had just hung on to outdated software and expected staff to muddle through to success. When that didn't happen, they blamed the software and not the strategy. Everything was in German, so rather than risk misinterpretation I turned to German-speaking friends in the technology industry to explain the report to me (if I got anything wrong, please tell me - the documents seemed very complicated).

My (guided) reading shows three points of concern in the situation over the last four years. First, the only ongoing expenditure in support of the migration is running costs of less than €15 per seat per annum, all associated with licensing supposedly superceded proprietary software. Second, substantial one-off costs of around €231/seat associated with interoperability - a topic that is always an indicator that proprietary software is controlling people’s thinking. Third, no obvious investment in ongoing community engagement or equivalent commercial subscriptions for open source.

"Very good article," Matthias Kirschner calls it. He is right. Phipps did a fine job and he should know. He was overseeing a lot of aspects of OpenOffice.org for several years at Sun. He also led some efforts to spread ODF and opposed Go-OO, whose team moved on to LibreOffice.

As we showed before, Microsoft had also used OOXML to derail the kind of migrations we saw in Freiburg. Those who were paid by Microsoft to pretend to support OOXML were also to blame. They helped legitimise it. It was always disguised as "choice", where one choice was lock-in, i.e. no choice. For proprietary software lobbyists, to be "neutral" is to choose proprietary lock-in, as shown in this new article:

Two members of Congress, reaching across the partisan divide, are pushing the government to think broadly -- governmentwide -- about open-source software, provoking warnings from industry groups that they are ignoring the core principle of technology neutrality.

No, this is not such a matter. To deny choice using lock-in is not to be neutral, it's to be predatory.

Anyway, one can hopefully grasp the similarity between the two cases; when Microsoft introduces new FOSS-hostile traps it requires that some "useful idiot" -- either paid or unpaid -- 'proves' that the traps are digestable. An effective diplomatic approach is to reject what is worthy of rejection, not give up. This is not a compromise, it is giving up/surrendering to Microsoft, ⬆