Language Selection

English French German Italian Portuguese Spanish

Microsoft and "Interoperability"...LOL! That's a good one!

While reading through srlinuxx's news posts, I was eventually led to Mary Jo Foley's (MJF) article regarding MS-Novell deal.

Microsoft-Novell: What a long, strange year it’s been
http://blogs.zdnet.com/microsoft/?p=916

The basic gist is that MS has been doing their usual patent FUD, while Novell is sprouting how wonderful interoperability is. Same agreement, two different views. Now that's odd. Typically, you'd expect all parties involved in an agreement to be singing the same tune.

So what's going on here?

Well, someone points out the obvious. This is TechExec2's post in MJF's article feedback:

Quote:
VERDICT: Microsoft's cynical patent FUD campaign is a DISMAL FAILURE

Let's be honest here. Microsoft doesn't want to "interoperate" with Linux. Microsoft wants to EMBRACE AND DESTROY Linux. Fortunately, as is often the case when Microsoft gives the "bear hug of death" and then tries to stab the victim in the back, they often miss. This case is no different.

From Microsoft's press release:
http://www.microsoft.com/presspass/press/2007/nov07/11-07MSNovell1YearPR.mspx

"...Having exceeded their original business targets, the companies continue to see strong demand for interoperability and intellectual property (IP) peace of mind..."

So... they are selling "peace of mind", huh. This is a tacit admission that the campaign is about fear, not business and legal reality.

Major corporations are NOT buying into Microsoft's patent FUD

Microsoft claims success and cites 30 companies. Where are the major corporations? General Electric? Proctor and Gamble? Citicorp? Bank of America? The rest of the "Fortune 500"? The fact that major corporations are not buying into this tells you everything you need to know.

Linux Distros are NOT buying into Microsoft's patent FUD

In the first year, Microsoft has signed up only four Linux distros:

1. Novell - Desperate for the cash they received from Microsoft in the deal.

2. Xandros - A small commercial Linux distro.

3. Linspire - A small commercial Linux distro.

4. TurboLinux - A small commercial Linux distro.

Meanwhile, two very large Linux distros, RedHat and Ubuntu, have already publicly said they are not going to sign patent deals with Microsoft. I applaud and cheer them. Theirs is the correct response to Microsoft's cynical patent FUD campaign.

This is about FEAR, not "interoperability"

And, the "interoperability lab"? This is just PR spin. Eight staffers and only 2,500 square feet? Microsoft is sending four of the "best and brightest" they have? Baloney!

For Microsoft-Novell lab, eight is enough
http://www.news.com/8301-13580_3-9776042-39.html?tag=blog.9

Pride goeth before the fall. Microsoft's cynical patent FUD (Fear-Uncertainty-Doubt) campaign against Linux is a DISMAL FAILURE.

Its not a failure...Its a joke. Just like the rest of the nonsense they've tried since the late 1990s. (When they saw opensource as becoming a major threat to their fundamental business model).

Here's another joke:

OpenXML/ODF Translator Add-in for Office project.
http://odf-converter.sourceforge.net/index.html

Notice MS's contribution?
"Funding, Architectural & Technical Guidance and Project co-coordination"

Can someone please explain what EXACTLY (details and specifics please) Microsoft contributes to this project? Do they submit any code related contributions? Or do they just hire third-parties like they usually do?

Instead of writing a damn plug-in that requires one to need MS Office, why not offer a multi-platform standalone application that reads (not edit/save), displays (for before and after comparison), and converts? Oh that's right, silly me! It won't force people into a corner such that they must need MS Office!

But of course, MS's vision for "interoperability" has many facets. One includes...

Steve Ballmer: "I would love to see all open source innovation happen on top of Windows"
http://blogs.cnet.com/8301-13505_1-9793052-16.html

Let's call MS's "interoperability" campaign what it really is. Its a farce of half-hearted attempts to LOOK like they're doing something (for their Press Releases, EU, and public), but not really achieving anything substantial if they don't see or get any direct benefit from it. When it comes to standards, it must be standards made by them, that they control and lead. (Which means they control the tempo of when new features and changes are released...They'll be your friend now, simply out of convenience to them).

Take for example, their Silverlight solution. They're only helping Novell with Moonlight on Linux so they can use their solution to crush their real target...Adobe's Flash.

Their thinking of standards is already well documented in Halloween documents 1 and 2. Its basically summarized as this: extend existing protocols and develop new protocols.

The Samba project has demonstrated that we do NOT need Microsoft involvement, input, or their patent covenants to achieve true interoperability. We can do it without them, its just a pitty that some commercial distro providers (Xandros, Linspire, etc) don't see that.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

Interop != open standards

Never was. "Interoperability" is a weasel phrase.

More in Tux Machines

Leftovers: OSS

  • Anonymous Open Source Projects
    He made it clear he is not advocating for this view, just a thought experiment. I had, well, a few thoughts on this. I tend to think of open source projects in three broad buckets. Firstly, we have the overall workflow in which the community works together to build things. This is your code review processes, issue management, translations workflow, event strategy, governance, and other pieces. Secondly, there are the individual contributions. This is how we assess what we want to build, what quality looks like, how we build modularity, and other elements. Thirdly, there is identity which covers the identity of the project and the individuals who contribute to it. Solomon taps into this third component.
  • Ostatic and Archphile Are Dead
    I’ve been meaning to write about the demise of Ostatic for a month or so now, but it’s not easy to put together an article when you have absolutely no facts. I first noticed the site was gone a month or so back, when an attempt to reach it turned up one of those “this site can’t be reached” error messages. With a little checking, I was able to verify that the site has indeed gone dark, with writers for the site evidently losing access to their content without notice. Other than that, I’ve been able to find out nothing. Even the site’s ownership is shrouded in mystery. The domain name is registered to OStatic Inc, but with absolutely no information about who’s behind the corporation, which has a listed address of 500 Beale Street in San Francisco. I made an attempt to reach someone using the telephone number included in the results of a “whois” search, but have never received a reply from the voicemail message I left. Back in the days when FOSS Force was first getting cranked up, Ostatic was something of a goto site for news and commentary on Linux and open source. This hasn’t been so true lately, although Susan Linton — the original publisher of Tux Machines — continued to post her informative and entertaining news roundup column on the site until early February — presumably until the end. I’ve reached out to Ms. Linton, hoping to find out more about the demise of Ostatic, but haven’t received a reply. Her column will certainly be missed.
  • This Week In Creative Commons History
    Since I'm here at the Creative Commons 2017 Global Summit this weekend, I want to take a break from our usual Techdirt history posts and highlight the new State Of The Commons report that has been released. These annual reports are a key part of the CC community — here at Techdirt, most of our readers already understand the importance of the free culture licensing options that CC provides to creators, but it's important to step back and look at just how much content is being created and shared thanks to this system. It also provides some good insight into exactly how people are using CC licenses, through both data and (moreso than in previous years) close-up case studies. In the coming week we'll be taking a deeper dive into some of the specifics of the report and this year's summit, but for now I want to highlight a few key points — and encourage you to check out the full report for yourself.
  • ASU’s open-source 'library of the stars' to be enhanced by NSF grant
  • ASU wins record 14 NSF career awards
    Arizona State University has earned 14 National Science Foundation early career faculty awards, ranking second among all university recipients for 2017 and setting an ASU record. The awards total $7 million in funding for the ASU researchers over five years.

R1Soft's Backup Backport, TrustZone CryptoCell in Linux

  • CloudLinux 6 Gets New Beta Kernel to Backport a Fix for R1Soft's Backup Solution
    After announcing earlier this week the availability of a new Beta kernel for CloudLinux 7 and CloudLinux 6 Hybrid users, CloudLinux's Mykola Naugolnyi is now informing us about the release of a Beta kernel for CloudLinux 6 users. The updated CloudLinux 6 Beta kernel is tagged as build 2.6.32-673.26.1.lve1.4.26 and it's here to replace kernel 2.6.32-673.26.1.lve1.4.25. It is available right now for download from CloudLinux's updates-testing repository and backports a fix (CKSIX-109) for R1Soft's backup solution from CloudLinux 7's kernel.
  • Linux 4.12 To Begin Supporting TrustZone CryptoCell
    The upcoming Linux 4.12 kernel cycle plans to introduce support for CryptoCell hardware within ARM's TrustZone.

Lakka 2.0 stable release!

After 6 months of community testing, we are proud to announce Lakka 2.0! This new version of Lakka is based on LibreELEC instead of OpenELEC. Almost every package has been updated! We are now using RetroArch 1.5.0, which includes so many changes that listing everything in a single blogpost is rather difficult. Read more Also: LibreELEC-Based Lakka 2.0 Officially Released with Raspberry Pi Zero W Support

Leftovers: Gaming