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
At this point, why not keep it going? Your story is good enough reason to keep working and build a community and/or foundation around AppGet.

>>ErikAu+Vn
Can't think of a more wasted effort then trying to compete with maintaining a package manager in your spare time than a clone from the OS vendor who can out resource, outspend, out market, out evangelize, out reach you, etc.

It would a futile endeavour, a realization acknowledged by the author, any further dev cycles on it would be wasted & are better spent elsewhere.

>>hizanb+Ko
The most cynic part of this story is sending him an email the day before the launch with a heads-up that WinGet was launching.

And the icing on the cake is the "btw, we are giving you the exclusive so keep it secret".

Like, wtf. He ain't TechCrunch. Why the fuck are they giving him that exclusive? Nothing yells "we stole your stuff, but dude it was open source so you really can't complain, and thanks for the idea" more than that.

You can't make up this shit.

>>whoisj+Dt
I mean, getting an email like that is bad, but it's better than not getting an email like that :D

Last year a huge game company released something built on my tiny open-source game engine (uncredited), and I only found out about it later from a kind internet stranger. All things considered, better to know in advance so you can at least have your own response ready, so you can comment in the relevant HN/reddit threads, etc.

That said, the "keep it secret" part of the mail here does sound weird, but given the other history there may have been an NDA in place.

>>fenoma+ty
But there is the promise of your OSS engine being used again, future potential. Microsoft essentially cut this person off from being involved in the future of Windows packaging and only told him 24 hours in advance. I'd need that amount of time just to process.

>>tiles+kA
Sure, all I said is that getting the email is better than not getting it. Obviously his case was worse than mine, the one just reminded me of the other - partly the lack of credit, and partly because the company in my case was owned by Microsoft.