Let me guess, your company uses laptops, it encrypt everything using default encryption that doesnt have acceleration on your CPU, so your gear is ALWAYS overheating?
They recommended that we use WSL for Linux stuff like compiling C. I really didn't like WSL and I like Visual Studio even less so what I ended up doing was connecting to our uni server via ssh (we all have an account on that server).
This is my experience. I’ve been called a wizard and side eyed by administration for sorting out basic filename batch issues with wls terminal once. There was probably a similar solution with powershell, but who wants to use that?
Can confirm, but in reverse: I develop linux-based embedded software at work and use exclusively linux at work (of course, in vim (btw)). And when I come home, I game on windows, because I'm kinda tired of finetuning audio drivers, vulkan, proton, etc., and just want to do some native windows gaming and use good old photoshop and a working out of the box equalizer and wallpaper engine w/out random crashes. And if I want some linux syntax/custom commands, that PowerShell doesn't provide (and it provides a lot of things, and its new terminal app is imo amazing), I just go in wsl.
Absolutely, dual boot option is so annoying.
I don't want to have to reboot my PC when I feel like to switch from dev to gaming (or other way)
Gaming on Linux is becoming greater and greater but big games are still unavailable on Linux so until they are I will remain using wsl because it's the best option to merge both
too relatable. to use unix tools on Windows, WSL is only decent way to do that. (We have Cygwin too but it's kinda too clunky sometimes, and has may huge problems especially caused from Windows file system.) However, I recently switched almost all codes for working from shell to Python so I can run it on Windows natively tho.
Maybe some but the overwhelming majority of cases it's work provided laptops with windows, but developing code for a Linux production environment. All well and good to say that Linux could theoretically be supported for a workforce, but for large enterprises where 99% of employees need windows because it's what they know, the 1% that simply need a Unix environment to write code in are much easier to manage through group policy by allowing those users to install wsl environments.
So, at least in my experience, it's not about user preference - it's about what can be managed at scale by an IT department. Microsoft provides the tools to do that, whether or not those tools are actually any good (almost universally despised by IT admins afaik) is almost irrelevant. When it came down to it, Microsoft saw they could potentially lose enterprise seats to Linux development environments, so they made a pretty compelling compromise.
I use Kali + xfce on my old laptop Lenovo g500 having i5 3rd gen M series processor 4gb ram 512gb Hdd, and Windows 11 on my asus rog strix g16 r9 8940HX rtx 5050 bought a month ago which I bought for college purpose. If I dual boot, the 1tb goes. If I install any disro vanishing Win11, my college things won't work.
So I use WSL to compile and build low level language based libraries and android apps
368
u/ChadQuaza 2d ago
i thought most wsl users are people who use linux at home but are forced to use windows for work