Comment on After 114 days of change, Broadcom CEO acknowledges VMware-related “unease”
QuaternionsRock@lemmy.world 3 months ago(probably shouldn’t) HyperV
What makes you say “probably shouldn’t”? WSL use is widespread at this point
Comment on After 114 days of change, Broadcom CEO acknowledges VMware-related “unease”
QuaternionsRock@lemmy.world 3 months ago(probably shouldn’t) HyperV
What makes you say “probably shouldn’t”? WSL use is widespread at this point
thesmokingman@programming.dev 3 months ago
WSL is also shit for any kind of containerization and HyperV fucks up everything else. If you’re not doing any DevOps/SRE stuff WSL 2.0 is fine provided you don’t mix the filesystems. I have been so frustrated with their claims on release for 1.0 and 2.0 that I haven’t evaluated the recent systemd release for WSL. I provision WSL for people that don’t know why they should care and Linux VMs for people that need to work with CI tooling.
In general if you use a Microsoft tool you have to use the Microsoft ecosystem. Sometimes that’s not a huge deal, eg VS Code just adds a ton of telemetry and GitHub reads all your public code. Sometimes it’s a huge deal, eg you want to do literally anything beyond Docker Desktop defaults in the container world.