Could you elaborate on what benefit these aliases will bring in your opinion? Some package managers like apt or yum don't ship with command aliases and others like zypper or eopkg do but those are actually only shortened versions of their long forms, e.g.:

eopkg

zypper

Different package managers use different command for the same action. For example, in apt you use remove while in Homebrew, Chocolatey and WinGet you should use uninstall. This can cause confusion to some users: A and B are synonyms literally, and command A works in some package manager, why does WinGet requires you to use B?

The example in #334 has shown such confusion: a long-time Chocolatey user simply finds winget find not working. "Find" and "search" are synonyms, so it will be more user-friendly to make find and search even lookfor(maybe) work.

Actually Chocolatey has done this: choco find and choco search are aliases for each other. WinGet should make words with similar or same meaning do the same thing, or at least, provide smart auto-correction advice.

If anything, the verbs should be the same ss the verbs you'd use had the team done the sensible thing and implemented winget using PowerShell cmdlets.
There is no good reason for losing consistency when consistency can be delivered easily.

If you use PowerShell Verbs, then you could also use the verb aliases.

WHY are people trying to reinvent the wheel?

If anyone has any strong opinions on aliases, i.e, if any others should be added, please post a comment on the linked PR

Where ever possible make aliases that are consistent with PowerShell. I know the team do not want cmdlets, but let's not diverge just because you can. Even if that boat has sailed