The_Decryptor

the drivers and communications to talk to printers are all closed source

That hasn’t stopped CUPS

Good news, they’re making it easier to fix stuff like “spurious double clicks”.

https://who-t.blogspot.com/2025/05/libinput-and-lua-plugins.html

True, that’d definitely make it a lot more viable to hold corporations to account.

It’s an easy license to reason about, allows for basically any project to use it, and you don’t need to worry about trying to enforce it (Because the GPL is only as good as your lawyers are)

Plan 9 is inspired by UNIX (Helps that it had the same devs), but it’s not a direct continuation.

UnixWare is I think the only direct continuation of the original AT&T UNIX. The various BSDs are close enough but were re-written entirely in the late 80s/early 90s so there’s nothing original remaining.

Should be possible, as it’s a normal VM you can already install flatpak apps in said VM as normal, you’d just need a Windows side bit to invoke the install within WSL when you opened the flatpak bundle, and then something to add a start menu shortcut from the app inside the VM (Which I actually assume already exists, I never actually ran WSL2 when I was on Windows)

Why have a laptop or a dual boot with Linux when you can now more easily stay on the proprietary OS ?

This is called market retention.

Preventing migration to another OS, another software ecosystem.

The ‘Embrace’ and ‘Extend’ parts of EEE.

That’s stretching the definition to the point it’s nearly unrecognisable.

What the term meant was for things like Internet Explorer, where MS adopted an existing standard (Embrace), started changing it in incompatible ways (Extend), while using their market power to lock out competitors (Extinguish)

e.g. IE used an incompatible method for sizing and laying out elements than any other browser, so a site that laid out properly in NN4 looked broken in IE6, and vise versa. So most devs targeted IE6 as it was more popular, and NN4 users got more and more broken sites.

ACPI was similar, Windows had an extremely lax implementation of it, so motherboards often shipped with bugs that Windows would ignore but would stop anything else from booting. Intentional? Doesn’t really matter, since it sure was helpful in slowing the adoption of things like Linux, that had to come up with workarounds for all the broken hardware.

Not like you can fork it to run on a different OS.

For WSL1? yep that’s effectively impossible.

WSL2 is effectively just a wrapper around the kernel virtualization support and a bundling format, as long as whatever image you run talks to the host properly (like any other virtualised OS would) it’d run.