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
From the article:

> Do you want to know how Microsoft WinGet works? go read the article I wrote 2 years ago about how AppGet works.

>>ahmeda+Zm
This is very unhelpful - I'm not really in a position to code review Microsoft's implementation and compare it to this document. I was hoping for something more like some high level details from the author of AppGet.

>>13of40+Ho
No one's asking you to compare. He's just saying winget works exactly the same as appget. So you can read that article about appget to learn how winget works.