It’s the best if you convince your boss that you need it for work in your non admin privilege system because you can sudo inside there so you can install whatever.
WSL has replaced my use of the command prompt in Windows for anything (and I used it more than most, I think).
In my job, I develop Linux applications to support industrial automation, and WSL is capable of building and running most of what I make. It isn’t a full Linux machine, and can behave unexpectedly when trying to do things like changing certain network configurations.
So it’s great for what it’s for, really. But if you want a full VM, this isn’t really for that.
There’s honestly not a lot of practical uses for it when you have the option of just running a Linux Distro anyway. It’s mostly to keep people who NEED to run Linux for work in Windows as an OS. Otherwise, I’ve found no purpose for it. Neat I guess? Useful, no.
When I used wsl, it felt fine. There were some problems with running more GPU intensive tasks, but being able to use linux-only software while I was restricted to Windows was pretty good.
I’ll parrot the others. I have a Windows PC issued by my employer. The only way to have some Linux is WSL. I use it to sync notes with server at home, python stuff, and w3m when I want to Google something without looking conspicuous in the office.
General Linux tools also help. I needed to make video half the speed - one liner ffmpeg solves it in a jiffy. On Windows I need to install some hive software.
WSL in Windows Terminal is not much different from opening Konsole on any regular desktop Linux distribution. I use openSUSE Tumbleweed on WSL and I think it’s great.
Add comment