[lionkor]

I dont really see the answer to the question in the article, maybe I missed it.

You can use PowerShell on Linux. You can use vcpkg on Linux (very well, even). You can learn C++ and you wont need the `_In_` and whatnot. If you use WSL2 for your development, are you even developing (fully) on Windows?

What you can't do is really own a copy of windows (any recent one), and have the freedom to decide what tools you will use. There is nothing protecting your system from locking you out of any setting, at any point, and requiring you to buy a different key, subscribing, giving them your data, or whatever else.

[secstate]

This, a million times. I am not principled enough to live without closed source hardware and software. But I've experienced too many changes to tools I didn't ask for and didn't want to try to advocate that closed source is better than open source alternatives.

[shortrounddev]

> If you use WSL2 for your development, are you even developing (fully) on Windows?

Maybe it wasn't clear in the post: I dont use wsl except as a backend for docker. I use powershell, not bash

> There is nothing protecting your system from locking you out of any setting, at any point, and requiring you to buy a different key, subscribing, giving them your data, or whatever else.

Thats not something I care about

[secstate]

> Thats not something I care about

Well what's the point in having a debate about any of this if you've yet to experience closed source software taking something away from you?