| Not disagreeing with you, but I think it's better to make it a little bit more clear what exactly was copied. Reading the article mentioned in the OP, the main selling point for appget seems to be that the packages are written in yaml: > Do you want to know how Microsoft WinGet works? go read the article (https://keivan.io/appget-what-chocolatey-wasnt/) But that alone doesn't particularly strike me as a completely novel approach on its own. Looking at package definitions for firefox across various package managers, you can notice that they all look somewhat similar to some degree. Though one could argue that appget and winget looks more similar than others, I'm not sure this is wholesale copying without digging into more details. But again, I'm not trying to argue that it's not, and I also agree the OP should've received more credit. appget: https://github.com/appget/appget.packages/blob/master/manife... winget: https://github.com/microsoft/winget-pkgs/blob/master/manifes... scoop: https://github.com/lukesampson/scoop-extras/blob/master/buck... homebrew cask: https://github.com/Homebrew/homebrew-cask/blob/master/Casks/... That being said, the fake interview process explained in the article is totally unacceptable and deserves some explanations from MS. |
It's literally the new cuddly microsoft Embracing, Extending and Extinguishing this guy's work.