Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

The Day AppGet Died

keivan.io

Post reply on HN
Print view View original

351–360 of 566 posts

Re: The Day AppGet Died

#351

Post by ChrisMarshallNY »

I remember the "good old days" of the Microsoft Borg.

They were infamous for getting small companies in under NDA, then grabbing their tech, and dumping the small companies (often putting them out of business). They are not alone in this (Apple has done the same thing. I think they even have a term for it -"to Watson" * ). It's just that MS was the most egregious.

It makes me sad to see they are still doing it. I've been fairly impressed by what Nadella has done.

* EDIT: As adamdavidson pointed out, the term that everyone uses is "Sherlocked."

Re: The Day AppGet Died

#352

Post by pwdisswordfish2 »

Posts critical of Microsft usually draw a set respone on HN. It has evolved over time.

1. Please stop picking on Microsoft, it is unfair

2. Microsoft has changed, look at ____ and _____

I am curious what the next one will be.

Re: The Day AppGet Died

#353

Post by zmmmmm »

allenu wrote: post #108

This was definitely not a great experience, but my hunch is what happened is some higher ups decided no, they don't need to hire you, the original team tells recruiting to notify you, recruiting drops the ball somehow, team goes on with their lives believing that you were told they were no longer interested, and everyone (except you, since you never got notified) believed the whole thing was resolved. The original pe…

No experience at Microsoft but plenty with lawyers in large corps and I would rate another possibility highly, which is that the team wanted to contact him but lawyers recommended "no further contact" as the safest legal IP path. Essentially, they were trying to close the barn door on clean-rooming the software and any further conversation could leak non-open-source ip that would then bring about a liability later on.

Re: The Day AppGet Died

#354

Post by foolmeonce »

deno wrote: post #324
TAForObvReasons wrote: post #279

Earlier 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 Hello darkness, my old friend…

Yeah I hope the TLD read is that this article has nothing to do with Microsoft embracing Linux and Debian distribution related tools are safe?

I would have preferred irrelevantGet but WinGet is unambiguous enough.

Don't work for free on proprietary systems or single sponsor opensource is a lesson cheaper learned by watching others.

Re: The Day AppGet Died

#355

Post by bryanrasmussen »

corobo wrote: post #343
bryanrasmussen wrote: post #308

Earlier quoted context omitted.

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

thanks, that explains it. seems trivial though, but I'm not a tech blogger.

Re: The Day AppGet Died

#356

Post by amdavidson »

ChrisMarshallNY wrote: post #351

I remember the "good old days" of the Microsoft Borg. They were infamous for getting small companies in under NDA, then grabbing their tech, and dumping the small companies (often putting them out of business). They are not alone in this (Apple has done the same thing. I think they even have a term for it -"to Watson" * ). It's just that MS was the most egregious. It makes me sad to see they are still doing it. I've…

I believe the more common version of that term is "Sherlocked"

Re: The Day AppGet Died

#357

Post by aerique »

pgt wrote: post #347
tarsinge wrote: post #313

Earlier quoted context omitted.

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.

There will be newer people after you flocking to the new Microsoft. Given how scummy and bad they have been in the past and how many people have been cheerleading them here, do you really think it works that way?

When people were warning against Microsoft on this forum they were just set aside as cynical, grumpy Unix-beards. If that happens even here, what do you think will happen elsewhere?

Re: The Day AppGet Died

#358

Post by mikorym »

TAForObvReasons wrote: post #279
dmix wrote: post #264

Earlier 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...

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

This comment should have a dualised state: downvotes that push it higher and upvotes that push it lower.

Re: The Day AppGet Died

#359

Post by toyg »

wwwigham wrote: post #302
toyg wrote: post #288

Earlier quoted context omitted.

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.

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 s…

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.

Re: The Day AppGet Died

#360

Post by andrewnicolalde »

Fredej wrote: post #282
renewiltord wrote: post #242

Earlier quoted context omitted.

The big companies often end up ghosting the guys they don't want to hire. A long time ago, I was an intern and got fully ghosted by Nvidia. It was very annoying but my life probably worked out better for it.

There's a big difference between ghosting and sending a mail informing you that the process has stopped. I realize I'm missing some context here, but I can't see how your life would work out better from _not_ receiving a heads up that the process has ended.

I think maybe he means that he feels better off no longer being associated with a company that wouldn't give him the benefit of that letter.
Post reply on HN