Live data from Hacker News

The Windows Subsystem for Linux is now open source

blogs.windows.com

971–980 of 1001 posts

Re: The Windows Subsystem for Linux is now open source

#971

Earlier quoted context omitted.

Hm. I used Git on WSL1 for many years, with medium sized repos hosted on a Windows drive, and it worked great. When I moved to WSL2 Git became a whole lot slower - it now takes about 5-8 secs to execute 'git status' where before it was instant.

Are your git repos in ntfs? WSL1 Linux drives are slow and in WSL2 Ntfs.

Yes, exactly, this is well known. So the parent post seems incorrect.

Re: The Windows Subsystem for Linux is now open source

#972
post #961

WSL is a landmine of bad design. I lost all my data once, and that incident made me switch to a Mac. Here's how you can lose all your data - and Microsoft engineers won’t care: https://github.com/microsoft/WSL/issues/8992 https://github.com/microsoft/WSL/issues/9830 https://github.com/microsoft/WSL/issues/9049#issuecomment-26...

I read your issue, and it's not so different from `sudo rm -rf /` as opposed to an actual design flaw.

`sudo rm -rf /` requires you to be a superuser or provide a password, whereas running `wsl --unregister` does not require elevated privileges.

Re: The Windows Subsystem for Linux is now open source

#973

Earlier quoted context omitted.

I know -- I was super excited to see WSL1 and wished it worked. NT when started was the OS/2 personality and back at that time was excited to see NT as the OS to end all OSes (by running them all as a personality). But WSL2 is freaking incredible, I'm super excited to see this and just wish the rest of windows would move to a Linux kernel and support bash natively everywhere. I was never a fan of powershell, sh/dash/…

>But WSL2 is freaking incredible It's good. But if/when you start using it as your main work platform nagging issues start cropping up. The native linux filesystem inside it cannot actually reclaim space. This isn't very noticeable if you aren't doing intensive things in it, or if you are using it as a throwaway test bed. But if you are really using it, you have to do things like zero out a bunch of space on the WSL…

Or just go straight to Hyper-V, without all the WSL stuff.

Re: The Windows Subsystem for Linux is now open source

#974

Earlier quoted context omitted.

What 3D modelling were you doing that couldn't be done on linux?

Fusion360 doesn't work on Linux. Or at least I tried multiple times and couldn't get it to work

Really? I recall installing it 3 years ago, and aside from some oddities with popups, it worked just fine. I think it was this script [0]. I don't know if they broke it, I switched to OpenSCAD, which meets my needs.

[0] https://github.com/cryinkfly/Autodesk-Fusion-360-for-Linux

Re: The Windows Subsystem for Linux is now open source

#975
post #845
post #504

Earlier quoted context omitted.

To the tech savvy, there is essentially only one advantage to running Windows, and that is the ability to run Windows-only software. In all technical respects - control, performance, flexibility - it is inferior to the alternatives. Don't confuse vendor lockin with technology. I find it dismaying that people on Hacker News willingly submit to incredibly user-hostile behavior from Microsoft and call it "the best of bo…

There is an additional reason: Some (many?) people simply prefer the Windows UI conventions (once you remove all the enshittifications post Windows 7).

I'm not aware of any particular UI convention that's in Windows that isn't available in, say Plasma. Day to day usage is extremely similar, and where they diverge it's usually because 1) Plasma has a feature that Windows doesn't, or 2) someone at Microsoft opted for senseless change for change's sake - a toy interface is layered over a functional one, often (but not always) grudgingly allowing access to the old behavior with extra steps, in a tacit admission of no-confidence. This behavior is pervasive - the "new control panel", the new context menu ("show more options" to get to the original, an extra click that yields a menu with many of the same options but in a different order with different icons), and best of all moving the "Start button" to the center - a change which more than any other exemplifies the silliness, because it 1) at best achieves nothing, and 2) flies in face of the original UI research based on Fitt's Law that informed 30 years of Windows UI tradition.

I honestly can't imagine anyone preferring all that.

Re: The Windows Subsystem for Linux is now open source

#976
post #151

When WSL came out I was absolutely overjoyed - finally an actual linux shell on windows! I use windows for my gaming pc, and I wanted to have a unified gaming/dev box. It felt like the solution. Over time though more and more small issues with it came up. Packages working not quite right, issues with the barriers between the two, etc. It always felt like there was a little bit more friction with the process. With Val…

I'll take Linux seriously when I can play Starcraft 2 and Fortnite on it

I played starcraft2 13 years ago on Linux, the wizard installer worked just fine.

Re: The Windows Subsystem for Linux is now open source

#978
post #820

Earlier quoted context omitted.

In general you want to avoid Nvidia if you want to play games on Linux, but maybe things will get better.

Isn’t pop_os shipping ancient components at this point due to their hate brained idea to try and create their own de and pinning their next release to it?

RDR is now working fine on Pop_OS with Proton 10.x.

Re: The Windows Subsystem for Linux is now open source

#979

Earlier quoted context omitted.

Unfortunately many of the more popular multiplayer games with anti-cheat tend to consider "made working on Linux" a bug rather than a feature. E.g. Easy Anti-Cheat and Unreal Engine both support Linux natively but Epic still doesn't want to allow it for their own game, Fortnite. https://x.com/TimSweeneyEpic/status/1490565925648715781

Nowhere it says they don't want to.

I think you're hitting on ideal vs. constrained wants (or, at least, that's how I've always referred to them). That is: what they want to be able to allow in itself vs. what they want to allow given the trade-offs with other wants.

E.g. "I'm going to go to the beach all day" and "I'm going to keep my job" are both likely the results of ideal type wants whereas "I'm going to go to my job today and then the beach tonight" would likely be the result of a constrained want.

Re: The Windows Subsystem for Linux is now open source

#980

Earlier quoted context omitted.

Unfortunately many of the more popular multiplayer games with anti-cheat tend to consider "made working on Linux" a bug rather than a feature. E.g. Easy Anti-Cheat and Unreal Engine both support Linux natively but Epic still doesn't want to allow it for their own game, Fortnite. https://x.com/TimSweeneyEpic/status/1490565925648715781

There is more nuance to the anti-cheat systems supporting Linux argument than "it supports it but they won't use it". Turning on Linux support does weaken the security posture of the anti-cheat system, so it's not simply a decision of "it works with Linux, but they won't do it". It is moreso a question of whether the security posture changes for the game with this platform support enabled meet the business requiremen…

Agreed, that's the angle Tim Sweeney argues in the linked comment as well.
Post reply on HN