With the way this world is going, your wish may come true with the ones left are going to be wearing Pip-Boy 3000's and paying with bottlecaps.

The code that they released as AGPL, but the CLA means that they own the copyright and can assign any license they please. So they can rerelease that code with any license they want.

So observing the license and threat of legal action is for all the other suckers that gave them free code.

The FSF is in favor of Contributor License Agreements that assign copyright. For example, in the GNU C Compiler contributing section:

CLAs that allow commercial entities to relicense and get sole full commercial use while burdening the community and competitors with a license so restrictive that it kills off forks is the monster of their creation.

*Accepted any merge requests by a contributor who didn't sign the CLA.

This is why Contributor License Agreements make most uses of AGPL be against the spirit of FOSS, because they usually allow the code to be relicensed. So AGPL is the millstone around the neck to prevent community forks or uses by competitors. Commercial organizations with actual resources to pick up the burden of maintenance won't want to get anywhere near the project with such a restrictive license.

So the most "Libre" of licenses is the most prominent enabler of commercial owners of projects to steal community contributions relicense to a commercial license for their own use. Then cut off the community as soon as the customer acquisition phase is over and they are ready to squeeze the money out of everyone.

The thing that Libre licenses were suppose to protect against are now used as the biggest cudgel.

Great, now we get to have weeks of stories about the stupid things that people can get the government chatbot to say.

Even his handle is a Pokemon reference.

• "What's your response to (insert AI concern here)?"
• "It's not AI, it's SI. Fake news!"

Meaningful response to legitimate concerns avoided!

We can continue to recycle this comment every time WSL gets a new feature. It's so creative, insightful, and has that slight anti-Microsoft slant that curmudgeon grey beards love.

Here's to another whole decade of the same comment repeated!

Rancher Desktop and Podman Desktop are both FOSS, very convenient, support compose and Kubernetes, and are listed in the summary.

Being native and pre-installed does make it a touch easier for the most basic use case, but it's not like it was hard before.

This isn't quite accurate, for many of the offerings there are multiple choices in "availability zones" with independent power, networking, and cooling either as a separate data or collection of centers within a region. For example, there are 6 AZs in the East region (e.g. Virginia).

You are right that C# is a good example of Microsoft behavior. Tying right into their nervousness on Java, it was proprietarily extending beyond the ECMA standards by layering on .NET. Around 2004 the Mono project pops up to try to cross-platform it, works but poorly, and a in a pretty sketchy patent situation. By 2009 the FSF warning everyone off of it, fearing that extinguishing play.

But by, 2014 Microsoft gives out full patent grants, open sources most everything, cross-platforms and makes Linux a first class citizen, creates the independent .NET foundation. buys out the Mono project, MIT licenses Mono, and donates Mono to the WineFoundation.

Basically the only way Microsoft is making money off of C# these days is full Visual Studio, noting of course that they open sourced VS Code. As for failed, C# still one of the top ten language in use and basically the defacto video game language.

So, you might want to do some reading that's more than a decade old on the topic. Because again there's a dark history and it's fine to be skeptical. But it's counter productive to hate on changed behavior.

Many of their tools like Office 365 or the Azure console are run in the browser. Are you advocating for traditional JavaScript without typing or pure WASM for those cases?

I understand the hate on JS/TS in the backend (and even in this article they are stating that Rust and the C's are the choice for backends), but pretending that TS isn't the only good choice for browser frontend apps seems silly.

This also implies that the money is being made on the OS. And everyone knows that the money is really in the App Store and Services.

This isn't even a recent development, PowerShell migrated from being under the OS section to the Azure section a decade ago because that's what was really making money.

You should clarify what open standards you think are being extended in a proprietary way in this case. Because that's the meaning of "Extend".

Oxidizer is MIT licensed, there isn't any proprietary version of Rust being sold. Just using the language to make their product better and then contributing back changes and tooling to the community.

They deserve all the hate for the late 90's with their extended proprietary JVM or with playing dirty in office file format standards with Open XML. But those are a decade and a half ago.

Using a tool and giving back is the premise of open source and giving grief over changed bad behavior is pretty counter productive to progress.