ChromeOS's Linux support is even more streamlined than Windows's approach. You enable it, the container is automatically created (though, it is possible to install other distros -- but you void official ChromeOS support), and then graphical apps just work. All window management works across Linux, Android, and ChromeOS apps seamlessly, and even the open with dialog in the ChromeOS file manager shows apps across Linux, Android, and ChromeOS. The app launcher also includes Linux apps.
One unique "feature" I like about the setup is how easy it is to just delete the container and start-over if I'm so inclined. I have an elaborate set of scripts to bootstrap a newly created Linux container on ChromeOS -- if anything goes wrong, I can just delete the container and re-run the bootstrap scripts.
I'm a big fan of where ChromeOS has headed and I like the containerized approach to the problem a lot. It's extremely close to getting to the point where I'd consider ChromeOS over MacOS for a work laptop, especially since they added Desk/workspaces support. I use ChromeOS exclusively at home and for personal dev now.
I'm kinda curious if in some wild future WSL3 ends up being Windows completely ditching the NT kernel for linux kernel and building up wine to be a first class Windows API emulator.
It's just increasingly silly in the Azure and server space to be running Windows--you lose all the benefits of the container ecosystem and have all the baggage of decades of windows cruft (yes I know windows containers exist--no one uses them). Desktop usage has been in decline forever and I have to imagine they could get the 90% of windows API apps left that matter to work great on wine. It would give Microsoft a huge boost to get back in ARM by building on the linux kernel and its great support vs. windows ARM very limited set of qualcomm and a handful of other chips.
AFAIK Windows is still one of Microsoft’s golden geese. If they transitioned to Linux, they’d lose out on all that sweet, sweet licensing revenue. Which makes this seem unlikely to me.
Last I heard internally there hasn't even been an official Windows OS team for the last couple years after Myerson left. It's been divvied up and split apart into parts of Azure, etc.
Yes, technically it is, but it's the integration that makes it interesting.
Plus theres the simple reality that Microsoft's got native APIs in Windows that enable running a linux vm with a KDE window alongside the standard windows environment. Microsoft has really come a long way and that's what's really amazing and kind of disorienting.
WSL2 uses it's own init system - only one kernel (plus a tiny initrd) is virtualized by hyper-v; each subsequent linux instance (distribution) is containerized. There's additional facilities that handle resource allocation dynamically vs the user specifying a static amount during VM creation.
These (and more) result in the end-user interacting with WSL2 the same way they would any normal application. To think of it as simply a VM isn't quite correct.
So I fired up Ubuntu first for my current WSL2... then I installed a Kali distribution.. are you saying that the Kali instance is really just a container inside the Ubuntu WSL2?
Not quite. WSL2 dynamically uses resources as needed (`vmmem`), whereas a traditional VM requires allocating a fixed amount of RAM and CPU from the host machine.
One unique "feature" I like about the setup is how easy it is to just delete the container and start-over if I'm so inclined. I have an elaborate set of scripts to bootstrap a newly created Linux container on ChromeOS -- if anything goes wrong, I can just delete the container and re-run the bootstrap scripts.
I'm a big fan of where ChromeOS has headed and I like the containerized approach to the problem a lot. It's extremely close to getting to the point where I'd consider ChromeOS over MacOS for a work laptop, especially since they added Desk/workspaces support. I use ChromeOS exclusively at home and for personal dev now.