Is this something to do with the three Es?
this post was submitted on 19 May 2025
722 points (97.5% liked)
Technology
70199 readers
3561 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
The 90s called, they want their joke back.
Great! With this source code out, I can finally complete the port to Linux. I call it WSL24L, aka "Windows Subsystem For Linux 2, For Linux"
Do you name every FOSS project? This is uncannily close to what an actual open source project would be called, including the logic behind it.
Nah, needs more recursion. The 'W' in "WSL" stands for "WSL"
Making WSL open source could actually lead to some useful contributions and better transparency overall ; and good for Linux tools?
I know there's a lot of hate for Microsoft on Lemmy, but WSL is one of the best parts of Windows. It's really powerful and well integrated to Windows. Since I still can't leave for pure Linux install, I'm glad for WSL.
Funny that the Linux is best part of Windows lmao
Microsoft hate is justified.
WSL made windows tolerable in the time I had to use a windows machine for work.
macOS is still the better choice for corp approved work, integrates decently with IT systems and is a “real” unix system underneath.
Linux on a corporate desktop is mostly about how well you know the IT guys and do they trust you. And of course the software stack.
Linux on a corporate desktop is mostly about how well you know the IT guys and do they trust you. And of course the software stack.
I would say it depends more on the commitment of the IT admins to support and manage a fleet of Linux workstations. There are Linux "Active Directory" servers, configuration provisioning tools, ways to centrally and automatically rollout updates, etc. It really depends on if the IT guys invest the same amount of effort to support them or not.
2000 people, 3k+ devices and one dude wants a Linux laptop.
Not happening 😀
But it did work in a smaller company of around 30 people, mostly because the IT guy was a Linux user too
Easy fix, install proxmox and run corpo-os in that as well as a proper desktop os. Just need to max out the ram on the shitbox thet give you and now you can switch almost seemlessly
load more comments
(1 replies)
load more comments
(3 replies)
load more comments
(3 replies)
I still will never understand why it's not called Linux Subsystem for Windows.
There's a trademark for Linux so Microsoft can't name a product starting with Linux.
So they can use Linux in the name, just not at the beginning? We're so stupid. Can they do Windows Subsystem for Coke? Or Windows Subsystem for McDonald's? Or Windows Subsystem for MacOs?
Good gravy.
load more comments
(9 replies)
Still doesnt explain why it wasn't called Windows Linux Subsystem (WLS)
load more comments
(1 replies)
I think it is because Windows has many subsystems, it's just that you don't hear about most of them aside from WSL.
So it is referring to the particular Windows Subsystem (of which there are many) that can run or emulate Linux.
load more comments
(1 replies)
I got hung up on this before too but it's apparently "Windows Subsystem for (using) Linux"
load more comments
(1 replies)
This is for WSL2, not for WSL1. WSL2 is just a VM, not a big deal it it's open-sourced. WSL1 is superior to WSL2 in every way. BTW, WSL2 is not a continuation of WSL1, they are being developed in parallel. I still try to use WSL1 whenever possible. For Linux specific features, like systemd dependancy and mounting file systems, I'd use full-featured VM instead of WSL2.
I thought WSL2 had a few specific advantages over WSL1, something about disk writes and/or Docker? But yeah, WSL1 was such a cool concept. My understanding is they implemented all the syscalls and API in it so it's basically native.
I tried to use them, as I do most tools like that. On Windows I have always stuck with the MSYS environment that Git for Windows gives you. It's easy enough to work with and has most everything I care about. Plus it's easy to set up. With wsl it's more like a separate thing, it wasn't as easy to run in place. A lot of times I still used batch or powershell scripts so it wasn't totally bash. Like Docker is easier to use from not bash in Windows because the syntax is so wonky.
But now I don't use Windows at all.
I've recently started using windows again for work, after not touching it for like 15 years, msys2 makes it tolerable.
I'm a devops engineer, and my company won't allow me to use WSL. Go figure.
MSYS2 is odd, I could never figure out how to set it up a sort from the one with Git. When I was more of a power user I used Cygwin. Babun is cool but unmaintained last I remember, and is just Cygwin with some enhancements.
As much shit as MS gets (and rightfully so) around 2019 they began turning their reputation around for dev stuff. They've lost all that good will though.
I could never figure out how to set it up a sort from the one with Git.
That's because the one provided with git is a nerfed version of msys2. If you install msys2 as a standalone thing from their website, you get everything you need for a functional CLI on windows. Most importantly, you get a real package manager and decently populated repositories.
but.. you need to run it on microsoft, which isn't open source....
Only right now. I'm sure someone will have it running on Wine or Proton by next week. Steamdeck subsystem for proton for Windows subsystem for linux
brb running vim on windows subsystem for linux on proton on wine on linux.
Just to confuse any computer virus.
Don't you think this is another Embrace, Extend, and Extinguish strategy from Microsoft?
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.
load more comments
(6 replies)
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.
load more comments
(4 replies)
load more comments
(36 replies)
fuck microsoft and windows so hard. had to reinstall that shitshow on my mothers computer because a driver update fucked the whole networkstack... they throw error codes and what not but give no help whatsoever. the conclusion of everyone for every problem is to reinstall windows.... shitshow of an os, keep your dirty hands of linux!! can't wait to nuke it and install linux there and have no windows machine left
load more comments
(2 replies)
I am legit excited to install WINE Subsystem for Linux
Or how about KDE on ReactOS on WSL?
The possibilities are endless
load more comments
(5 replies)
Pretend I'm an idiot (should be easy), and tell me what this all is up in here.
Classic Microsoft Business Strategy
- ~~Embrace~~
- Extend
- Extinguish
Means that now anyone can fork the project and make changes or iterate on it without needing to wait for Microsoft to fix things.
load more comments
(2 replies)
view more: next ›