13 karma · joined May 15, 2020
When you are programming against an API, you are using the interface. When you use an interface, you are a user. You are even the expected User from the API designers perspective. You are that API designers customer. In your job as the User of that API, you also have different customers you serve. But that doesn't mean you are no longer a User of the API. Because you are the user in this case, using an API, then that must mean your going to have a User Experience with that User Interface that just happens to be in a API.
MS already had a "package manager" called OneGet. They also have a package manager called NuGet.
I don't see any issue with MS replacing OneGet with WinGet.
Or why the name WinGet offends AppGet, or AptGet, or OneGet, or NuGet, etc.
I think [name]Get is pretty common.
I've been working on a graph database, and would love to have some feedback, and if it's your thing, some help. I'm happy to answer any questions.
Cheers!