Re:WSL2 corrupting Git repositories and shell history
by kalium-xyz on Saturday January 02, 2021 @05:57PM
(#25617430)
I've recently come across the same issue with DAWs. Settled on having multiple machines and switching the drives if I need to reuse a workstation for something else. Most of the time you can dedicate cheap systems to specific utilizations, it will save you time and effort. e.g. There is no reason for your DAW machine to also be your gaming machine as the hardware requirements are pretty different.
Re:WSL2 corrupting Git repositories and shell history
by qppo on Saturday January 02, 2021 @09:23PM
(#25618747)
It seems fairly expensive to have different machines for gaming and music production/recording when the only substantial difference is relative investment into CPU and GPU cycles.
Re:WSL2 corrupting Git repositories and shell history
by kalium-xyz on Monday January 04, 2021 @05:02AM
(#25629405)
You dont need new computers for everything. Older machines are often super cheap and saving them from getting scrapped reduces ewaste.
Re:WSL2 corrupting Git repositories and shell history
by iakov on Sunday January 03, 2021 @10:40AM
(#25622345)
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.
Re:WSL2 corrupting Git repositories and shell history
by bashwizard on Monday January 04, 2021 @03:23AM
(#25628863)
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 has a low entry cost since you basically only need a decent amount of ram. My studio computer has an old i7, 32 GB ram and it doesn't even have a GPU and the price was less than $500 a few years ago. It's going to outlast my current gaming rig and probably my next one as well.
Re:WSL2 corrupting Git repositories and shell history
by iakov on Monday January 04, 2021 @07:56AM
(#25630694)
I'm making music for a few years, and for at least two years my Windows workstation has been the main piece of gear.
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
by nijaru on Saturday January 02, 2021 @05:52PM
(#25617391)
I’ve always solved this issue by keeping windows on one drive and linux on another. It does have an upfront cost, but keeping my dev work / linux environment setup has always worked well for me. Lately I’ve thought of trying WSL, but I don’t see any real benefit over my current setup
Re:WSL2 corrupting Git repositories and shell history
by kalium-xyz on Saturday January 02, 2021 @06:01PM
(#25617447)
IMHO dedicated environments encourage mindsets specific to those environments thus make you more productive. Would not switch to not having them.
I expected to hate it, but I'm asking myself why I didn't do this sooner.
It's the same sort of scenario as before -- I have Windows running the games I occasionally play, and music stuff, and I do all of my code stuff in WSL2/Ubuntu.
But this way, I never have to fiddle with weird WINE patches or googling bugs, everything "just works". Asking myself why I didn't do this sooner to be honest.
I had one big complaint which is that copying files from Windows to WSL2 would create ".ZoneInfo" file copies of every file, that was downloaded from the web, but they patched this recently too.
With the support for Linux GUI apps that launched with Windows Insider Preview recently, I have a hard time making arguments against it now. The taste of crow is a little bitter, eh.
Linux + WINE/Proton basically felt like shittier, more bug-ridden Windows + WSL2. With the one notable exception that as an OS/host, Windows 10 "feels" a bit slower in general.