The Day AppGet Died (opens in new tab)

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.

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

To be honest, after a year of constantly having to follow up and not hearing back, it gets exhausting. Also, I did follow up on Feb with the HR rep due to some expense issues, Also asked them about the update on the interview. She promised someone will get back to me. Which obviously never happened.