Remind me please, which of these is shipped with a default Windows install?

I realize you asked sarcastically, but as of relatively recently WinGet is shipped by default with the latest versions of Windows 10 and in Windows 11. [1]

But why is being installed by default important?

[1] https://www.petergirnus.com/blog/how-to-use-windows-package-...

It's an adoption barrier.

I know very non-technical people who use Chocolatey for acquiring ffmpeg.

meh. it's not.

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.

IMHO it is though. I have a windows VM I rarely use and tried using a package manager at some point, but end up not succeeding until winget was part of the system and was a no-brainer.

Too many possibilities made me choose none.

It was only partially sarcastic (yeah that didn't communicate at all, bad habit on my end), I had googled them but didn't quite understand the winget situation at glance. Thanks for the answer, actually appreciated!

I don't know why you're being downvoted, but distributions for Windows would be really popular. A server distribution of Windows would help its adoption a lot.

The same that shipped with a default UNIX install.

Most of those are for installing applications, not system-wide C library source distributions (e.g. you'll need to figure out the path of the source and header files in build scripts since there's no standard location for that on Windows).

The closest thing to a C/C++ package manager standard on Windows is probably vcpkg: https://vcpkg.io/en/