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
I can say I’m a bit upset on your behalf. Actually acquiring the code would have cost Microsoft very little money, would have ended up with a better product and also would have brought along the current user space in a very graceful manner.

>>hmotte+5x
They didn’t even need to acquire - MIT license means they could just fork it and use it as they preferred, keeping his name in the About screen that nobody reads. But it would have looked bad.

So they did this and... it looks even worse.

>>toyg+dT
There's no common code between the projects; they're not even written in the same language. It's hard to say it's a "fork". They both just use yaml manifest files on GitHub as a registry (which could be good for appget! It should be easier to set it up as a trusted package registry with verified non-malicious packages!). That's the commonality. I'm not sure we should grant monopoly on _broad architure choices_ when software patents are already considered so toxic. And appget _did_ at least get a callout in the release announcement, so it _was_ mentioned as an inspiration, in the same breath as chocolatey and others...

The meat of this blog post, to me, seems like the terrible hiring pipeline with no feedback. That seems like a really bad experience. I can only imagine that someone really dropped a ball somewhere.

>>wwwigh+4X
Nobody talked about granting monopoly, it's just about common courtesy really. They basically strung him along before cloning his tool in the dark, when they could have done it in the open in various different ways. After the failed hire, just give him a heads-up like "hey, we really like your stuff but for various reasons we can't hire you and we need to rewrite it, what about we make this manifest a bit of a common standard? We'll credit you for that", and then everyone is happy.

>>toyg+Rc1
this.