Anybody who thinks running Windows is easier hasn't tried to get Tensorflow working on Windows with GPU support.
In theory, it could run on a straight Windows build of Python, but nobody seems to have given that serious consideration. It must go through WSL, but that means passing through the GPU to WSL. When you Google how to do it, you'll find three different approaches that have been taken over the years, only one of which is valid on modern setups. If you take one of the old approaches, you will likely twist your system in knots and need a complete reinstall to fix.
On Linux, you install the GPU drivers, compile Tensorflow with the GPU flags, and you're done.
The best Windows tweak script is here
ohyou dot jaypeg
nah, the real GOAT is https://get.opensuse.org/tumbleweed/
This is so true. Most of the tools justifying the use of WSL aren't even supported. Either because of technical limitations or because of security concerns.
Why do people use wsl? The only reason I can think of is to take advantage of Bash and the shell environment. But if wsl runs in its own container separate from Windows, what's the point?
When WSL first came out, all the documentation i read from Microsoft led me to believe it was intended to help developers who are cross-developing software for both Linux and Windows to more easily test features and compatibility and to ensure software behaves consistently. It never seemed like they intended it to be used to run Linux programs fully and integrate into the Windows environment. It always seemed like it was just there for convenience so a smaller budget developer could develop on one machine and not need to be constantly rebooting or running VMs.
Being a software developer but your work laptop is a Windows machine?
Maybe I'm not aware of similar configurations you can do, but it's only sorta it's own container. VSCode can actually directly connect to it automatically so you can develop in host os but run directly against the container. Additionally this means some visualization/gui interfaces can be visible on the host side (this is a gift and a curse).
So you basically have system integrated containers/vms. It's not perfect, but it is definitely leagues better than what windows development was prior and may have some advantages over Linux only deployments (not sure if the system integrations are feasible in Linux hosts).
Linux using wine and bottles:👁👄👁
Should use Linux Subsystem for Windows instead.
Wine would like a word
I was just thinking this. If you're dev, being on pure Linux makes a ton of sense. But if you're a gamer, Windows is still your best option.
Why would anyone want this? I don't get it. I haven't needed Linux for anything in years. I actually run docker for Linux stuff (mostly for fun) and it works if you're competent (same as anything Linux related, it requires work.)
Oh sorry, I forgot where I am. Windows bad! BAD WINDOWS.
I could ask the same. Why would anyone want windows? I haven't needed windows for anything in years. I run wine for windows stuff(mostly for fun) and it works if you're competent.
Seriously tho, I care about my privacy somewhat, and a lot of my hardware just doesn't run windows because it's too heavy. I also dislike the lack of control I have over windows and can't work with the windows DE in general.
mingw64 and cygwin
