Language Selection

English French German Italian Portuguese Spanish

GitHub as the Latest Example of Microsoft Entryism in Free/Libre Software

Filed under
Just talk

"This is in effect the very same trick they did/pulled with Novell and SUSE (where Nat Friedman came from after his Microsoft internship) about a decade ago."

Postman

THE recent GitHub takeover, which has not formally been approved just yet (although there are no foreseen barriers to it), is definitely bad news; it is a lot of things to Microsoft however. It is good news only to Microsoft and GitHub shareholders, who basically sold out many developers without rewarding/compensating them for this unwanted (to them) takeover.

There are many aspects to it: First of all, it helps paint Microsoft as "open source" and it helps Microsoft gain leverage over developers, e.g. their choice process of framework/s and licence/s (Microsoft still dislikes copyleft); by leverage over platform they can suggest Azure, for example, or create bindings to it; they gain leverage over projects tied to governments, including some of our clients at work; Microsoft can vainly tell them, i.e. the governments and their developers: "look, you want FOSS? We're FOSS" (so they effectively become their own competitor!). In fact, there's so much more and I could easily name a couple dozen examples, but I know people pursue/need concision here. For an analogy, in politics this concept or strategy is known as "entrism" or "entryism".

Microsoft also uses patents to blackmail FOSS; there's that element too, albeit many people conveniently choose to forget it. Microsoft is sending patents to patent trolls, then offers "Azure IP Advantage". This is in effect the very same trick they did/pulled with Novell and SUSE (where Nat Friedman came from after his Microsoft internship) about a decade ago.

There are many other angles to it, including programming languages, frameworks (e.g. proprietary IDEs like MSVS), code editors and not just bindings to Microsoft as a host and API provider. People, especially developers of software, generally know how E.E.E. works; the basic precondition/premise is that you gain controls/leverage over that which threatens you (Nokia: Elop, Novell: Mono and lots more examples). So that's kind of a way of getting inside, gradually forming a partnership and then shutting down or sidelining whatever threatens you. Like Xamarin did to RoboVM, in effect killing it under Friedman's leadership. Friedman is going to be the chief of GitHub.

Microsoft can direct the opposition's decisions and its fate. Sadly, they already do this inside the Linux Foundation, where Microsoft staff already has chairs in the Board.

From what I can gather, developers ditching GitHub is becoming a fairy common thing this month. I already see the 1) active 2) large 3) non-Windows ones leaving, but it can take time; some told me they still rely on open bug reports and other 'vendor lockin'; that needs some work before they can migrate; the real alternative is self-hosted git.

"Sadly, they already do this inside the Linux Foundation, where Microsoft staff already has chairs in the Board."

More in Tux Machines

Mozilla Leftovers

  • Firefox Nightly: These Weeks in Firefox: Issue 91
  • Phabricator Etiquette Part 1: The Reviewer

    In the next two posts we will examine the etiquette of using Phabricator. This post will examine tips from the reviewer’s perspective, and next week will focus on the author’s point of view. While the social aspects of etiquette are incredibly important, we should all be polite and considerate, these posts will focus more on the mechanics of using Phabricator. In other words, how to make the review process as smooth as possible without wasting anyone’s time.

  • Robert O'Callahan: Visualizing Control Flow In Pernosco

    In traditional debuggers, developers often single-step through the execution of a function to discover its control flow. One of Pernosco's main themes is avoiding single-stepping by visualizing state over time "all at once". Therefore, presenting control flow through a function "at a glance" is an important Pernosco feature and we've recently made significant improvements in this area. This is a surprisingly hard problem. Pernosco records control flow at the instruction level. Compiler-generated debuginfo maps instructions to source lines, but lacks other potentially useful information such as the static control flow graph. We think developers want to understand control flow in the context of their source code (so approaches taken by, e.g., reverse engineering tools are not optimal for Pernosco). However, mapping potentially complex control flow onto the simple top-to-bottom source code view is inherently lossy or confusing or both. For functions without loops there is a simple, obvious and good solution: highlight the lines executed, and let the user jump in time to that line's execution when clicked on. In the example below, we can see immediately where the function took an early exit.

  • Marco Castelluccio: On code coverage and regressions

    There are two schools of thought when it comes to code coverage: those who think it is a useless metric and those who think the opposite (OK, I’m a bit exaggerating, there are people in the middle…). I belong to the second “school”: I have always thought, intuitively, that patches without tests are more likely to cause postrelease regressions, and so having test coverage decreases risk. A few days ago, I set out to confirm this intuition, and I found this interesting study: Code Coverage and Postrelease Defects: A Large-Scale Study on Open Source Projects. The authors showed (on projects that are very different from Firefox, but still…) that there was no correlation between project coverage and the amount of bugs that are introduced in the project and, more importantly, there was no correlation between file coverage and the amount of bugs that are introduced in the file.

today's howtos

Nvidia GPU Passthrough To Windows VM From Linux Host

Nvidia has now officially enabled GPU passthrough support for Windows virtual machines on GeForce graphics cards. In other words, this effectively means it?s possible to run a Linux machine and then run a virtual Windows machine within it, and hand that unfettered access to a graphics card. This is a big win for those wanting to run Windows games from within a virtual machine on your Linux desktop. They will be able to play Windows-based games using a virtual machine with GPU passthrough enabled. Read more

IBM/Red Hat/Fedora Leftovers

  • Red Hat Satellite 6.8.6 has been released [Ed: They have unpublised this since.]

    We are pleased to announce that Red Hat Satellite 6.8.6 is generally available as of April 13, 2021.

  • A brief intro to Red Hat OpenShift for Node.js developers – IBM Developer

    Container-based deployment models are the modern way to develop and deliver your applications. The most common tool for building with containers is Kubernetes, an open-source container-orchestration system for automating computer application deployment, scaling, and management. Kubernetes has helped usher in a standardized way to deploy and manage applications at scale, but it can be a sprawling, difficult beast to manage when your application becomes more mature and more complex. A company will need to have a robust DevOps team to manage a full-fledged Kubernetes-based production system. [...] My colleague, JJ Asghar summed it up nicely: “OpenShift provides creature comforts to talk to the Kubernetes “API”—at the same level of robustness—as long as you’re willing to use the opinions OpenShift brings.” The good news? Those opinions are tried and tested, enterprise-ready choices with the backing and support of Red Hat. So, what do Node.js developers need to know about OpenShift deployment? This blog post covers the “what” and “how” of deploying your Node.js application in an OpenShift environment.

  • Fedora Community Blog: Community Blog monthly update: March 2021

    In March, we published 21 posts. The site had 5,520 visits from 3,652 unique viewers. 888 visits came from search engines, while 450 came from the WordPress Android app, and 386 came from Twitter and 208 from Reddit.

  • How Red Hat data scientists use and contribute to Open Data Hub

    Artificial intelligence (AI) and machine learning (ML) drive much of the world around us, from the apps on our phones to electric cars on the highway. Allowing such things to run as accurately as possible takes huge amounts of data to be collected and understood. At the helm of that critical information are data scientists. So, what’s a day on the job look like for data scientists at Red Hat? Don Chesworth, Principal Data Scientist, gives you a glimpse into his day-to-day in a short video (aptly named "A Day in the Life of a Red Hat Data Scientist") that’s now available on our website. Isabel Zimmerman, Data Science Intern, provides a look at some of the tools she uses on the job in "Using Open Data Hub as a Red Hat Data Scientist." We’ll cover some of the highlights in this post.

  • IBM Brings COBOL Capabilities to the Linux on x86 Environment

    IBM has announced COBOL for Linux on x86 1.1, bringing IBM's COBOL compilation technologies and capabilities to the Linux on x86 environment. According to the IBM announcement, COBOL for Linux on x86 can help modernize, integrate, and manage existing applications, data, and skill sets to ease an organization’s transformation into a more flexible business. To connect business components with suppliers, partners, employees, and clients, and to position organizations to quickly take advantage of opportunities and respond to challenges in real time, COBOL for Linux on x86 can help meet these challenges and enable use of existing COBOL code while upgrading applications with the newest technologies.

  • <./ul>