Mate, that sucks. Sorry, fuck those dick heads. That email, meant to aswage their guilt, hey we gave _you_ knowledge of the release date, don't you feel special. Its like people pushing infront of you on the road, nearly making you crash and then thanking you. Grrrr
The Day AppGet Died
341–350 of 566 posts
Re: The Day AppGet Died
#342Earlier quoted context omitted.
Hopefully they also weigh in the fact that screwing developers over is terrible publicity. Assume 100k developers see this and are slightly less inclined to trust MS in future, this bad publicity could easily cost them 1mn USD plus. A good will gesture of 100k USD at the start for consulting could have saved everyone a lot of trouble. See https://news.ycombinator.com/item?id=23332123 elsewhere in this thread for an e…
I find MS seems quite immune to terrible publicity in the recent years. "But it's not the same company as before! They are doing open-source now!" yada yada
Lots of open source services springing up...that only run on CosmosDB.
Re: The Day AppGet Died
#343Earlier quoted context omitted.
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…
what is the point of an exclusive if you have to keep it secret - I mean if he were TechCrunch for example, if he got the exclusive I guess he should publish, isn't that the point of an exclusive? I find it a very confusing phrase.
To get your article pre-written and ready to publish the moment embargo lifts.
As opposed to the other tech bloggers who will have a scramble to write it after hearing about it with the rest of the world
Re: The Day AppGet Died
#344Earlier quoted context omitted.
In all fairness: - "NuGet" is super-popular in .NET circles (included in Visual Studio by default) - "apt-get" is the classic tool for Windows Subsystem for Linux So "WinGet" certainly "makes sense" as a name without being a direct ripoff of AppGet
> "apt-get" is the classic tool for Windows Subsystem for Linux APT is the classic tool for debian-like Linux distributions. FTFY
Get used to it, this is going to be the bulk of the "Linux" users from now on.
Edit: Imo not a bad thing, it's just how it is. A lot of people will learn (of) Linux through WSL. Linux as a runtime.
Re: The Day AppGet Died
#345Earlier quoted context omitted.
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.
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.
He only asked for acknowledgement.
And lets not forget - they had similar open source project and community. They decided not to participate but create their own. This new project will overshadow existing and eventually kill community.
Re: The Day AppGet Died
#346Author 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…
Ah yes. The new Microsoft, same as the old Microsoft.
I am really sorry this happened to you. On the scale of Microsoft, or even on the scale of what they're putting into this effort, it would have cost approximately nothing to give you an "acquisition" you would have been happy with. If the job didn't work out, they could have given you a fat consulting contract for a year or two. Or they just could have written you a check.
And it would have cost them actual nothing to just treat you with respect. Say how much they loved your work. Credit you publicly as a leader and an inspiration. Arrange a smooth transition for your users.
For what it's worth, I'm glad for you that the job didn't happen. Much better to be far away from people like this.
Re: The Day AppGet Died
#347Earlier quoted context omitted.
Hopefully they also weigh in the fact that screwing developers over is terrible publicity. Assume 100k developers see this and are slightly less inclined to trust MS in future, this bad publicity could easily cost them 1mn USD plus. A good will gesture of 100k USD at the start for consulting could have saved everyone a lot of trouble. See https://news.ycombinator.com/item?id=23332123 elsewhere in this thread for an e…
I find MS seems quite immune to terrible publicity in the recent years. "But it's not the same company as before! They are doing open-source now!" yada yada
They are not immune. As someone who has been supportive of Microsoft getting their act together, and who recently spoke at a Microsoft-sponsored conference, this stuff makes me hesitant to give any Microsoft-owned properties money and discourages me from trying new Microsoft products.
Re: The Day AppGet Died
#348After reading the second e-mail it is clear that they are trying to do something "official" and that their interest in the specific person is low (to say it mildly). Full of "going-forward" and similar corporate-speak. DANGER DANGER DANGER: when someone loses natural language, he is no longer speaking for himself. What a pitiful world we live in.
> As you know we are big fans of package managers on Windows and we are looking to do more in that space.
that part looked wrong
Re: The Day AppGet Died
#349Author 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…
Sorry for your shitty experience. Really reminds me of Robert Kearns who's windshield patent was stolen by big auto companies [0]. Robert patented it but still megacorps tried to screw him over because they thought they could. He did win but only after an exhausting trial that took years. Really sucks when credit is not given where due. [0] https://en.wikipedia.org/wiki/Robert_Kearns
It reminds me even more of Stac Electronics: https://en.wikipedia.org/wiki/Stac_Electronics#Microsoft_law...
In 1990, they put out Stacker, which did transparent disk compression, effectively giving people twice as much disk space. It was a huge hit, so Microsoft called them up about an acquisition, entered discussion, and as part of the due dilligence process, even looked at the source code.
In 1993, Microsoft released their own version of Stacker as part of the OS. No thank you, no money for Stac, just a giant middle finger. Stac sued and eventually won some money, but it was never the same.
Everybody keeps telling me that Microsoft is different these days. About how they love open source now. And it's true that after decades of erosion of their primary monopolies, they can't get away with being as lazy and awful as they were in, say, the early IE era. But this suggests to me that deep down they haven't really changed.
Re: The Day AppGet Died
#350Author 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…
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...
> Calling it "WinGet" was the real punch in the gut.
I feel for the guy, but someone who called their package manager "app get" in 2014 when "apt get" has existed for since 1998 is in no position to take umbrage at a competing package manager having a six-letter name ending in get.