[rvz]

And then there were those who said Microsoft "has changed". Time and time again, their entire plan was to "use open-source" and "free" incentives to get into the developer market.

Unless it is a hardware or a software project of the scale of Chromium or GitHub with millions of users, there is nothing that can stop Microsoft from rolling their own version. This unfortunately just confirms that once again.

Typical EEE here.

[bb010g]

This isn't embrace, extend, extinguish, at least at the AppGet scope:

• Embrace: Microsoft privately contacted the single primary developer of AppGet (a package manager; libre, copyleft, Apache-2.0) about potential employment.

• Extend: Microsoft implemented WinGet (a package manager; libre, permissive, MIT) privately on their own, borrowing from AppGet's architecture (design-wise, not code- or library-wise).

• Extinguish: Microsoft publicly unveiled WinGet after providing advanced notice to two external parties, the development teams of the existing Windows package managers Chocolatey (which commercially sells functionality WinGet doesn't subsume) and AppGet (i.e. one person).

None of these are EEE, except arguably Extinguish with AppGet. But you're moving in that case from an Apache-2.0 licensed solution to a MIT licensed solution, when modern Microsoft has proven to have decent respect for their permissively licensed source releases. This is a phyrric victory for AppGet.

[nailer]

Microsoft did roll their own version, but it's Open Source: https://github.com/microsoft/winget-cli/tree/master/src