zlacker

>>lostms+(OP)
Author here, Because it's sure to come up here is a comment I wrote on Reddit that clarifies somethings, I haven't updated the original article since I'm not sure what the etiquette for updating a highly shared article is.

------

Code being copied isn't an issue. I knew full well what it meant to release something opensource and I don't regret it one bit. What was copied with no credit is the foundation of the project. How it actually works. If I were the patenting type, this would be the thing you would patent. ps. I don't regret not patenting anything. And I don't mean the general concept of package/app managers, they have been done a hundred times. If you look at similar projects across OSes, Homebrew, Chocolaty, Scoop, ninite etc; you'll see they all do it in their own way. However, WinGet works pretty much identical to the way AppGet works. Do you want to know how Microsoft WinGet works? go read the article (https://keivan.io/appget-what-chocolatey-wasnt/) I wrote 2 years ago about how AppGet works.

I'm not even upset they copied me. To me, that's a validation of how sound my idea was. What upsets me is how no credit was given.

>>kayone+Tk
Can you go into more detail about which features you believe were copied?

>>13of40+Cl
It’s mentioned in the article: “ the core mechanics, terminology, the manifest format and structure, even the package repository’s folder structure”

The manifest format is particularly egregious.

>>alasda+sq
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.

>>waon+LA
He's not claiming that his approach was "completely novel". He's claiming microsoft identified his way, that already existed, was the way they wanted to go, toyed with bringing him in to run it and then got overwhelmed by internal Not Invented Here / We Can Do It Better and threw him under the bus.

It's literally the new cuddly microsoft Embracing, Extending and Extinguishing this guy's work.

>>outsom+qJ
You are a small Team in a big company.

Your job is to create an App Manager.

There is already a code base under a MIT license.

You use it.

I'm not seeing the issue.