Earlier quoted context omitted.
You don't need it but it's 1/3 the price of an Apple workstation and just runs with all hardware compared to Linux. Plus, some people just like Windows and/or don't like macOS.
> runs with all hardware compared to Linux. No, it doesn't. Linux runs on more architectures than Windows. Linux supports a wider range of machine specs than Windows does. There has never been an operating system in human history having hardware support as vast Linux. The television in your living room might be running Linux. Your refrigerator might be running Linux. Your car might be running Linux. Linux is everywhe…
WSL2 corrupting Git repositories and shell history
411–420 of 423 posts
Re: WSL2 corrupting Git repositories and shell history
#412Earlier quoted context omitted.
There is no reason to have multiple computers, apart from a laptop and workstation for people who need to be able to work on the go. Not only upfront cost, but license costs, update management, hardware replacement and finally disposal and recycling are piling up. I fail to see the upside, honestly.
When you're starting out making music having just one computer for everything is fine but once you've reached the point where you spend a lot of your time on it, it quickly becomes a no brainer to at least have a dedicated computer for just that. It's about putting yourself in a productive setting where you only focus on creating and you have minimal distractions. Besides, a dedicated computer for music production ha…
I totally get what you mean by productive setting. I achieve that with two user profiles - one for music (dark colors, only DAW and GuitarPro, no social networks or messengers), another for fun (brighter colors, steam and battlenet). It is a much cheaper - free! - than $500, and I get to save some space at home.
In the end different strokes for different folks I guess. If your setup works for you - keep it up!
Re: WSL2 corrupting Git repositories and shell history
#413Earlier quoted context omitted.
We are talking about GNU/Linux here.
We are not. You are.
Re: WSL2 corrupting Git repositories and shell history
#414Earlier quoted context omitted.
Enabling hardware virtualisation opens up a significant and deep attack surface. Considering the vanishingly small percentage of users which benefit from it, I hope it stays off by default.
Erm, explain? What attack can you do with hardware virtualization enabled that you cannot otherwise do?
Re: WSL2 corrupting Git repositories and shell history
#415Earlier quoted context omitted.
Enabling hardware virtualisation opens up a significant and deep attack surface. Considering the vanishingly small percentage of users which benefit from it, I hope it stays off by default.
Are there significant risks from running virtualization locally like this? If so, can you provide any links or elaborate a bit so I can follow up? Most of what I've seen on such vulnerabilities refer to server infrastructure.
Re: WSL2 corrupting Git repositories and shell history
#416Earlier quoted context omitted.
Enabling hardware virtualisation opens up a significant and deep attack surface. Considering the vanishingly small percentage of users which benefit from it, I hope it stays off by default.
In Windows, enabling virtualization actually reduces attack surface. E.g. it is used to protect against kernel-level malware: https://www.techrepublic.com/article/how-virtualisation-is-c...
Re: WSL2 corrupting Git repositories and shell history
#417Earlier quoted context omitted.
We are not. You are.
That was the whole point of this thread, naturally some rather move goal posts to avoid the subject that Linux users rather give money to proprietary desktop platforms than help desktop Linux ever become a reality.
Re: WSL2 corrupting Git repositories and shell history
#418Re: WSL2 corrupting Git repositories and shell history
#419Re: WSL2 corrupting Git repositories and shell history
#420Earlier quoted context omitted.
Reminds me of an infuriating old bug in VirtualBox where it wouldn't notice the size of a file had changed. Devs were working in some Windows editor then using Git within VirtualBox to commit changes, resulting in inexplicable trailing nulls and garbage turning up in the repo Took quite some time to figure out what was causing it. "Everyone is somehow corrupting files except for me, wtf?" Magic filesystem translation…
I'm now in the habit of doing a git diff before every commit. Even if I don't thoroughly read the diff, I at least skim it for sanity. I can't recall what made me start doing that, but now it's a habit.
Same thing, sorta but all in one go.