The Day AppGet Died
491–500 of 566 posts
Re: The Day AppGet Died
#492Author 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 projec…
As author of an open source tool that was already steatlh-forked twice without any contact whatsoever by VC-backed startups - including clearly copying text from my website/FAQ - without giving any sort of credit on the idea/implementation they used for 80% of their product but on the contrary claiming how revolutionary their products are and best idea since sliced bread, and even not satisfying the basic MIT license…
Re: The Day AppGet Died
#493Earlier quoted context omitted.
As author of an open source tool that was already steatlh-forked twice without any contact whatsoever by VC-backed startups - including clearly copying text from my website/FAQ - without giving any sort of credit on the idea/implementation they used for 80% of their product but on the contrary claiming how revolutionary their products are and best idea since sliced bread, and even not satisfying the basic MIT license…
What is your open source tool?
Re: The Day AppGet Died
#494Author 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 projec…
I think I will not credit everyone on my comparison tables. I only credit who inspired me hugely. MS hasn't implemented everything AppGet had. I bet MS is waiting for public feedback for the next point. Acutally MS has its Roadmap: https://github.com/microsoft/winget-cli/blob/master/doc/wind...
For the spec, only two common options: YAML & JSON. And every YAML spec looks this way.
MS has other experiences like TypeScript Definition also. https://github.com/DefinitelyTyped/DefinitelyTyped/tree/mast...
Re: The Day AppGet Died
#495Earlier quoted context omitted.
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.
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" mo…
Re: The Day AppGet Died
#496Re: The Day AppGet Died
#497Earlier quoted context omitted.
Calling it "WinGet" was the real punch in the gut. Does Microsoft select for assholes or something? There's a thousand other package manager names [1] in the wild and they chose that one. So much for "developers, developers, developers"... [1] https://en.wikipedia.org/wiki/List_of_software_package_manag...
I would think that their old system of stack ranking would have had that selection impact. It has been gone for a long time but could it have had a lasting impact on company culture by who was being kept and who was promoted into positions that are responsible for the culture today? I don't think such a thought is unreasonable.
Re: The Day AppGet Died
#498I was curious about hearing Microsoft's side of the story. There's an existing issue filed against the winget repo for this, if you're interested, subscribe to the issue: https://github.com/microsoft/winget-cli/issues/353
Lets use github & opensource itself to ensure the Appget developers gets his fair share!
Re: The Day AppGet Died
#499Earlier quoted context omitted.
To me, context matters. 'AppGet' sounds like a friendly hat tip to the legendary apt-get, given that they don't compete. 'WinGet', a direct copy of 'AppGet', is not a friendly reference IMO.
And why is "WinGet" not also a reference to apt-get? I've never even heard of AppGet before this morning.
On the other hand "WinGet" sounds like "wing-it" i.e. release any piece of junk and fix later. Maybe. Which TBF does seem to be how Microsoft works anyway.
Re: The Day AppGet Died
#500Author 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 projec…
And what would be the benefit if Microsoft gave you credit for it? Most likely their lawyers would reject it since you may then be able to sue them for...I don't know what, but money in any case.
It's a very Microsoft-thing to do to copy someone else's idea and improve on it (C#, RDP, Excel). If you release something as open-source you have to ask yourself if your doing it out of altruism or for money? In case of the latter you have to plan accordingly, by patenting or with restrictive licensing.