This is a most excellent place for technology news and articles.
So besides the brownie points, im curious what having it open sourced will benefit. Not like you can fork it to run on a different OS. You can make some extensions but to do what? You can’t really tie it further in to the host OS unless you know of some undocumented Win32 APIs.
Maybe im just not thinking creatively enough.
They released their code as MIT which is far more permissive than I was expecting. I was expecting some sort of proprietary license.
But they need to keep doing stuff like this. Devcontainers for VS Code is still proprietary and keeps me from running codium.
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.
does that mean we could build a wsl that provides the flatpak environment, so that we could get a one click install flatpak for windows?
Watch someone reverse the thing into turbocharged WINE
The entire thing is for running Linux software on Windows, it's the complete opposite of Wine.
Pretend I'm an idiot (should be easy), and tell me what this all is up in here.
Means that now anyone can fork the project and make changes or iterate on it without needing to wait for Microsoft to fix things.
Ah, the Linux Subsystem for Windows (MSFT has never been great at naming things) is finally open source, hooray...
Now do it with rest of the operating system, and I may, possibly have a reason to care.
But it is not a "Linux Subsystem", it is a "Windows Subsystem".
If I write a hypothetical Driver for Linux to support windows, it would be a "Linux Module" not a "Windows Module".
I guess they could have called it "Windows Subsystem for Linux support"
some who can read code tell me why it sucks ass
1/10 no tutorial on how to jump over an office chair.
