I'm sure, but it's also "yet another package manager" because everyone has their own favourite package manager. It's a nit, but it's nice when a README.md goes "you need X, Y, and Z" and doesn't pretend you need a specific method for that. Tiny phrasing change, zero real world difference of course, but it's a nice little sign that the folks running a project know that you know what you're doing on the OS you're working with (either by choice, or by paycheque =)
Scoop is the main package manager I've been using for years on windows apart from chocolatey. Dunno many others aside from the official windows one: winget.
I've been using Windows as dev platform since it was called "DOS but don't look too closely", I know chocolatey, ninite, winget, and powershell's own built-in nonsense, and yet had never head of scoop until just now. So... that really just tells us that any application manager we think is popular, ubiquitous, and the obvious choice is still really just a niche program =(
Contrast that to brew on MacOS: ever non-devs know about brew.
And from all of those, which I'd heard of, I think scoop is the only one to allow a package author to just create a git repo, and publish a package that way.
Like brew does. That why I use scoop.
Chocolatey would rather charge money for that, for some reason, and people are still willing to donate them their free time.
