3 ms·

I feel like it would be useful to add "(using WSL)" to the title. I admit I would not have opened the link though, had the title spoiled this part of the story

by jraph 7y ago

I feel like it would be useful to add "(using WSL)" to the title. I admit I would not have opened the link though, had the title spoiled this part of the story, and the article is funny to read. > Running Wine on Windows has been a fever dream of those responding to the siren call of "we do what we must, because we shouldn't" since at least 2004, when someone tried compiling Wine in Cygwin and trashed the registry of the host system. […] > But I want to stress again: this now works trivially. I'm not some sort of mad genius to have done this thing — I only appear to be the first person to admit to it in public.

davidgerard 7y ago
WSL is part of Windows 10, so I didn't feel the title was leaving out something important.
- jraph 7y ago
  Well, you are right but I expected to find an article speaking about Wine running on native Windows without WSL, which would make it interesting in another way. I would not expect Wine not to run on WSL. What I learned from the article though is that WSL1 does not run 32 bit binaries (and that someone botched their registry trying to run Wine on Windows back in 2004, which I found funny).
  - coldpie 7y ago
    > Well, you are right but I expected to find an article speaking about Wine running on native Windows without WSL While it isn't all of Wine, it is a fairly well-known usecase to build certain Wine modules and run those on Windows. It's been used to support ancient games that depend on certain old quirks that have changed in more recent Windows. It's also used by graphics driver developers, because Wine's implementation works on both Windows and Linux, so they can study differences at the driver level on both platforms.