Slash Boxes

SoylentNews is people

posted by martyb on Wednesday June 12 2019, @10:05PM   Printer-friendly
from the same-old-M$ dept.

Microsoft's tactics against GNU/Linux have not changed much in two decades, they're just framed differently, nowadays the attacks are masqueraded as friendship and proxies are used more than before. So as a fresh look at how these established tactics are used currently to attack Free Software, a guest poster at TechRights has summarized them in a ten-chapter handbook, aptly named A Handbook for Destroying the Free Software Movement. The first two chapters cover what Microsoft is now doing through GitHub, licensing, Azure, Visual Studio, Vista10, and its other components foisted on developers. Other chapters cover manipulation of media coverage, OEM lock-in, use of attack proxies, and software patents. Most of all, these tactics have stayed true to the plans outlined over 20 years ago in the Halloween Documents.

  • Introduction
  • Chapter 01: Know your enemies– Act like a friend
  • Chapter 02: Work with the system– Use OEMs and your legal team
  • Chapter 03: Playing the victim– Show the world that too much freedom hurts development
  • Chapter 04: You get what you pay for– Getting skeptics to work for you
  • Chapter 05: Open Source Judo– How to bribe the moderates to your side
  • Chapter 06: Damning with faint praise– Take the right examples of free software and exploit them for everything
  • Chapter 07: Patent War– Use low-quality patents to prove that all software rips off your company
  • Chapter 08: A foot in the door– how to train sympathetic developers and infiltrate other projects
  • Chapter 09: Ownership through Branding– Change the names, and change the world
  • Chapter 10: Moving forward– Getting the best results from Open source with your monopoly

It's written a bit tongue in cheek from Microsoft's perspective. Some material is drawn from Comes v Microsoft (aka The Iowa Case) and, as mentioned, the leaked internal memos known as the Halloween Documents.

Original Submission

This discussion has been archived. No new comments can be posted.
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
  • (Score: 3, Insightful) by krishnoid on Wednesday June 12 2019, @11:13PM (1 child)

    by krishnoid (1156) on Wednesday June 12 2019, @11:13PM (#854900)

    Flashbacks are nice, but it would be great to have their actions as a timeline. That way we can remember what they did to their competitors -> how they spun it -> why the current release sucks -> why the new release will be better -> lather, rinse, discharge microplastics into the environment -> repeat, and at exactly which points we were naive enough to believe them, until we stopped.

    Starting Score:    1  point
    Moderation   +1  
       Insightful=1, Total=1
    Extra 'Insightful' Modifier   0  
    Karma-Bonus Modifier   +1  

    Total Score:   3  
  • (Score: 4, Informative) by JoeMerchant on Thursday June 13 2019, @01:54AM

    by JoeMerchant (3937) Subscriber Badge on Thursday June 13 2019, @01:54AM (#854962)

    So much hasn't changed. We're a mixed development shop: Windows10 and Ubuntu, and neither is perfect, but I see the Windows devs on the same f-ing treadmill that I was running back in the 90s, it never stops. When I finish something in Ubuntu, it stays finished. And, when there's a problem in Ubuntu, even the Windows guys can dig into the logs, find the problem, find the diagnosis on the web in 30 minutes or less, and have a solid fix plan. On the Microsoft side, when shit breaks down or doesn't perform as expected it's denial and obfuscation city: maybe you need to buy a better library? That's unsupported. This is the new behavior, maybe you should migrate your codebase to the new toolset?

    Україна досі не є частиною Росії.