Earlier quoted context omitted.
Except Wine cant cover all of Windows (partly due to fault of Windows). I can't run UWP apps for example. Windows is not a good operating system but if you need it. WSL creates way more intuitive working environment for you. So even if you can run multiple Linux OSes in Linux you can't run Windows as easily you can do linux on Windows. So OPs statement is not incorrect.
There are virtual machines for Linux with seamless window integration, so upgrading to Linux is still recommended imo. OP's statement remains incorrect, because their assumption is that the WSL experience can't be reproduced in Linux.
The Windows Subsystem for Linux is now open source
941–950 of 1001 posts
Re: The Windows Subsystem for Linux is now open source
#942Earlier quoted context omitted.
There are virtual machines for Linux with seamless window integration, so upgrading to Linux is still recommended imo. OP's statement remains incorrect, because their assumption is that the WSL experience can't be reproduced in Linux.
Still can't run everything. Especially apps or games that does vm detection.
Re: The Windows Subsystem for Linux is now open source
#943I still can't believe how people use windows as their main system with all the extremely invasive telemetry and bogus "AI" features that hogs a LOT of resources at idle
As a software dev I understand that having telemetry is a good thing. I dont believe it is "extremely invasive".
And I have no idea what AI features you mean (at least on Win10).
Re: The Windows Subsystem for Linux is now open source
#944Earlier quoted context omitted.
On linux it's quite trivial. KVM is part of the kernel. Installing libvirt and virt-manager makes it really easy to create vms. I'd say even passing through a GPU is not that hard these days though maybe that depends on hardware configuration more.
That really depends on what you want to run. Dipping into a Linux laptop lately (Mint) there are things, old things (think 1996-1999) that somehow "just work" out of box on Windows 10, but configuring them to work under WINE is a huge PITA coming with loads of caveats, workarounds and silent crashes.
Re: The Windows Subsystem for Linux is now open source
#945Earlier quoted context omitted.
The essential problem was that critical Windows APIs like CreateProcess and the NTFS file system were far too slow to be used in UNIX-like ways. If you tried to run git or build things in WSL1 - a key use case - it was way slower than doing so on native or VM Linux.
Win32 APIs like CreateProcess suck because they have to spend so much time setting up the stuff that allows Win32's application model to mimic that of 16-bit Windows, which was coopreratively multitasked. The NT kernel is much faster at creating processes when it doesn't need to worry about that stuff. As for NTFS: it's not NTFS specifically, it's the way the I/O system is designed in the NT kernel. Imagine any call…
Re: The Windows Subsystem for Linux is now open source
#946Earlier quoted context omitted.
>Given the layoffs round from last week, in a record earnings year, I wonder if this is a side effect of those layoffs. Decisions, preparations and execution to open source such projects in big corporations to not happen within a week, two or month.
you could probably say the same about layoffs
Managers learn about lay offs day or two before engineers
Re: The Windows Subsystem for Linux is now open source
#947Earlier quoted context omitted.
It's the other way around. You can do very few productive things with Windows other than software development. Almost all other professional software assume Windows.
> You can do very few productive things with Windows other than software development. I guess you meant Linux here
Re: The Windows Subsystem for Linux is now open source
#948Earlier quoted context omitted.
I would love to hear about these edge cases and which tooling fails to detect they they were launched form linux. Sounds a lot like a picnic problem but you didn’t give nearly enough details.
Yesterday, they tried to get a Python library that built a native library using Meson to work. They were working under WSL, but somehow, Meson was attempting to use the MSVC toolchain and failing.
One of the most common issues is calling a windows executable from within wsl… it’s a “convenience” feature that takes about 2 seconds to disable in the wsl config but causes these kinds of weird bugs
Re: The Windows Subsystem for Linux is now open source
#949Earlier quoted context omitted.
Performance was one problem, but imho the biggest was that MMAP semantics were inherited from the NT side and made a lot of applications crash (mmap's created could only be as large as the file's current size as in Windows, while Linux/BSD semantics allows for a mmap larger than the file that's usable without constant remapping as the file grows). They didn't prioritize it until fixing at a late stage, barely before…
> (mmap's created could only be as large as the file's current size as in Windows, while Linux/BSD semantics allows for a mmap larger than the file that's usable without constant remapping as the file grows). I thought you could do it using ntdll functions, no? https://www.jeremyong.com/winapi/io/2024/11/03/windows-memor...
Regardless this led WSL1 to have fatal incompatibilities for a long time, iirc basic stuff like the rpm system or something similarly fundamental for some distros/languages relied on it. And once WSL2 existed people just seems to have gone over.
Re: The Windows Subsystem for Linux is now open source
#950Earlier quoted context omitted.
I agree. Back in the day (10+ years ago), I used to argue with people about why I ran VMs instead of just partitioning the disk and booting up the OS I needed. XAMPP did not work out of the box with me on Windows (skill issue on my part, I know), so my preferred setup was to run a Ubuntu Server VM (LAMP stack) and then develop whatever I had on a Windows IDE. I could have done that under full Linux, I just did not wa…
> XAMPP did not work out of the box with me on Windows (skill issue on my part, I know), so my preferred setup was to run a Ubuntu Server VM (LAMP stack) and then develop whatever I had on a Windows IDE. Why wouldn't you have just spent 5 minutes to get XAMPP working?
LAMP stack worked for me perfectly on Linux out of the box, whether Ubuntu Server or any RHEL-based distro (even with SELinux enabled!).
I spent some solid 8+ hours on that, saw it uneconomical and went the VM way.