I am legit excited to install WINE Subsystem for Linux
Or how about KDE on ReactOS on WSL?
The possibilities are endless
this post was submitted on 19 May 2025
679 points (97.5% liked)
Technology
70173 readers
3881 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related news or articles.
- Be excellent to each other!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
- Check for duplicates before posting, duplicates may be removed
- Accounts 7 days and younger will have their posts automatically removed.
Approved Bots
founded 2 years ago
MODERATORS
Also try out winegui.
Don't you think this is another Embrace, Extend, and Extinguish strategy from Microsoft?
It's kind of the opposite in my mind, WSL is (was) Microsoft capitulating to the fact that Linux is not going away, same with Azure. WSL is mostly for companies. Some companies have a huge contract with Microsoft and manage all laptops with it. Then they grow big enough that they can't ignore Linux because they have people who need to work on Linux. WSL is the way Microsoft keeps their clients, because otherwise they move to Apple based IT.
EEE would have been investing in PowerShell, PuTTY, or similar.
I think it's an attempt to keep people on their platform who need easy access to a unix-like shell. Linux has it and so does mac os. Windows didn't until they introduced wsl.
Well windows had cygwin and mingw
I had to move back to those a few times instead of using WSL during the early days. There were quite a few growing pains.
Fixed it fully by installing Linux.
has, they still work great and keep me sane
MSYS2 is my current choice for GNU/Windows
load more comments
(1 replies)
That's exactly what it is. Any time now you'll see "the best way to run Linux: on windows" or similar.
Does Lemmy even know what EEE means anymore or are we regurgitating words we heard from some article now?
What's it going to embrace and extend? WSL has existed for ages and is just a way to run Linux in a convenient container on top of Windows. That's it. It's not an attempt to "extenguish" Linux, literally just make the development experience on Windows less painful so people don't switch to another OS. This has nothing to do with EEE.
Open sourcing it with a permissive license can only be a good thing, and again they're doing it to be more appealing to devs and maybe get free bug fixes from the open source community. It isn't some grand conspiracy. But of course this community will react to news of "proprietary blob is now open source" with pessimism.
literally just make the development experience on Windows less painful so people don't switch to another OS.
You said it right there yourself and don't seem to realize it.
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.
And if it works, then in a few years, MSFT will figure out how to further monetize some other part of its software ecosystem that is either reliant on, or much much easier for an average user of WSL to use than switching their whole setup or stack all the way over to Linux.
Call that EEM for 'monetization' if you want, or 'enshittify' for another E...
...the commonly used term to describe software or services or platforms that suddenly jump over to making previously free stuff cost money, put ads everywhere, break the previously free features and put the 'new' working versions behind some kind of paywall...
... All after you've captured your market and dominated as many competitors as possible.
Standard monopolist strategy throughout the entite history of capitalism, same general concept goes back even further.
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.
Linux is a standard they have Embraced.
As a for-profit tech monopolist, they will, very predictably, Extinguish the ability of people who use WSL instead of just actually Linux... to be easily able to... fully transition to a competitor (Linux).
The Extend part just looks different, because the scope of software competition offered by Linux is much more vast than just a particular standard for a particular kind of software.
... Potato, potato.
I used to work for Microsoft.
The ethos is absolutely still there: Create vendor lock in, create ecosystem dependence in every way possible, as well as in ways that 99% of people would not even think are possible.
EEE is just the term they came up with to describe their own, overarching, monopolist general strategy, and if you wanna quibble over the precise technicalities of an internal corporate slogan, well then you'd be the kind of person MSFT is filled with that made me no longer want to work for them.
load more comments
(2 replies)
I think it’s more embrace. They have to compete against so many more entities now.
load more comments
(10 replies)
I don't think that, as Microsoft hasn't done a lot (any?) of that stuff in recent years. It's good to be cautious but really what is the problem with opening the source for something that already existed for a while and is embraced by many?
load more comments
(2 replies)
Normally I would say yes, but WSL is so incredibly necessary for a developer that it might be legit.
load more comments
(1 replies)
load more comments
(16 replies)
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.
im curious what having it open sourced will benefit
MS won’t have to pay their own people to work on it anymore.
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?
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)
load more comments
(1 replies)
Fair play to Microsoft here. Hopefully we see some pull requests from non-ms employees and a better wsl experience for us all
