Live data from Hacker News

The Day AppGet Died

keivan.io

201–210 of 566 posts

Re: The Day AppGet Died

#201
Keivan obviously got screwed.

Having worked at Microsoft, and seeing the nature of the bureaucracy, the only advice I would give for next time is...

Just realize you can't set terms with a large company like MSFT unless you get lawyers involved early.

Stealing from you outright is simply too tempting, given their resources.

I noticed there were some conditions Keivan tried to set regarding the future evolution of the technology before joining MSFT.

In a large company like MSFT, there were bound to be large internal email threads relaying a play-by-play of negotiations with Keivan to: inside legal counsel, developers who already gave t-shirt sizes for building the tech in-house, product managers, and dozens of others.

No matter what they tell you, they're internally weighing

- Should we just rip him off? - Should we hire him? Would that be better or worse for liability? - How IP protected is this? How much can we "borrow"? - Is it worth the hassle of dealing with an aqui-hire we can't control? Would that expose us to even more IP risk, or less?

Once companies reach this size, they simply can't be trusted to handle a negotiation transparently and in good faith, unless you have well paid lawyers fighting for you, or well established IP protection.

I guess what I'm saying is...

When dealing with any large tech company with near infinite resources -- like MSFT, GOOG, etc --, find a legally defensible upper hand, and assume they are weighing the cost-benefit of screwing you.

(Sadly, this is exactly why lawyers make so much money.)

Re: The Day AppGet Died

#202
post #86

Earlier quoted context omitted.

Can you go into more detail about which features you believe were copied?

It’s mentioned in the article: “ the core mechanics, terminology, the manifest format and structure, even the package repository’s folder structure” The manifest format is particularly egregious.

Not disagreeing with you, but I think it's better to make it a little bit more clear what exactly was copied. Reading the article mentioned in the OP, the main selling point for appget seems to be that the packages are written in yaml:

> Do you want to know how Microsoft WinGet works? go read the article (https://keivan.io/appget-what-chocolatey-wasnt/)

But that alone doesn't particularly strike me as a completely novel approach on its own. Looking at package definitions for firefox across various package managers, you can notice that they all look somewhat similar to some degree. Though one could argue that appget and winget looks more similar than others, I'm not sure this is wholesale copying without digging into more details. But again, I'm not trying to argue that it's not, and I also agree the OP should've received more credit.

appget: https://github.com/appget/appget.packages/blob/master/manife...

winget: https://github.com/microsoft/winget-pkgs/blob/master/manifes...

scoop: https://github.com/lukesampson/scoop-extras/blob/master/buck...

homebrew cask: https://github.com/Homebrew/homebrew-cask/blob/master/Casks/...

That being said, the fake interview process explained in the article is totally unacceptable and deserves some explanations from MS.

Re: The Day AppGet Died

#203
post #104

Earlier quoted context omitted.

Ahem https://www.gnu.org/philosophy/enforcing-gpl.html

Have you actually read the essay to which you're linking? >Meanwhile, much murmuring has been going on in recent months to the supposed effect that the absence of judicial enforcement, in US or other courts, somehow demonstrates that there is something wrong with the GPL, that its unusual policy goal is implemented in a technically indefensible way, or that the Free Software Foundation, which authors the license, is…

Your implication that "untested in court" means "likely unenforceable" is quite wrong--unless you see lots of people openly violating a license in cases where it would be economic to pursue them, the more likely explanation for "untested" is simply that the accused infringers get competent legal advice, and comply without wasting their money on a losing court case. Though as other comments note, since the writing of that essay someone (D-Link) finally did refuse to comply without a court order, at which point Harald Welte took them to court and D-Link indeed lost.

And what do you think "not able to prosecute" means? District attorneys (or non-USA equivalents) decide when to prosecute crimes, not private copyright owners. It's very rare for the criminal justice system to intervene in complicated white-collar stuff, especially when a straightforward civil remedy is available. A legal realist might say that means the GPL--and indeed most copyrights beyond those infringed by warez/torrentz sites--is effectively unenforceable criminally, and would in a useful sense be right; but it's enforceable civilly, so no one cares much.

Re: The Day AppGet Died

#205

Earlier quoted context omitted.

Sounded like they wanted to hire you for their package manager and you chose not to pursue. You have every right to be mad I suppose but as you say in the article, and in that comment, you're definitely aware of what happens to open source projects. On the other hand I'm mainly glad their adaptation was open source. I think they have to maintain their own version in order to ensure that they don't wind up with some r…

From the article, it sounds like he did pursue. After some interviews Microsoft dropped contact.

Which I don't find all that weird. Quoting OP here; "after visiting the campus, I wasn’t too sure I wanted to work for such a big company, also moving from Canada to the U.S. wasn’t something I was too excited about".

In the past, I've been in talks with an employer about a job, and my enthousiasm was only so-so, and that tended to put a brake on the proceedings.

Re: The Day AppGet Died

#206
post #182
post #115

Earlier quoted context omitted.

Large corporations often have more to fear from the liability of bad PR than they do from lawsuits. Most CEOs hate bad PR more than paying out a billion dollar fine — the billion dollar fine isn’t their money, and doesn’t cost them any status at the country club.

I'm actually having a hard time imagining something like Sonarr making much of a negative pr splash. It doesn't download pirated shows, nor does it play them. It just organizes and renames and creates lists of missing episodes for files that may or may not be pirated content.

Mmmm... There is a certain segment of the tech industry that is morally opposed to piracy, and actively pursue those people. I know because I've seen the negative connotations they've received. Had a candidate with a homelab, peer inferred it was for piracy, didn't want to hire him because of that.

I've also seen it in the weebs and also brainwashing Japanese Corp culture.

I have a feeling because its m$ their cture dictates that they at least appear they were disgusted with his sonarr authorship.

Re: The Day AppGet Died

#207

Earlier quoted context omitted.

Windows NT is designed out of the box for extending and embracing Unix. The whole Linux Subsystem thing isn't something new that required deep reworking of the kernel.

The Linux Subsystem actually doesn't use the NT subsystem technology that you're thinking of. They did end up inventing a few new kernel concepts (like pico processes) in order to do WSL v1.

Indeed. There was a windows services for Unix subsystem based on Xenix mentioned elsewhere and that was based on the subsystem architecture.

When you use it, you get a nice Korn shell and it is built on PE binaries linked against PSDLL.DLL. there's a functioning but very old version of GCC that ships with it.

The PE binaries mark up the desired subsystem to be invoked so you don't have to be in the environment to execute one - the kernel takes over.

PSDLL acts as a translation layer for NT much as kernel32 does for win32. You can't run unmodified Linux binaries like you can with wsl. On the other hand, WSL requires that you invoke lxss with some special com magic to get access to Linux first so you can't just exec an elf file directly. The Pico processes you mentioned - these allow the kernel to install specific handlers/translators of their syscall functionality into the windows kernel.

So yeah architecturally they're pretty different and WSL isn't really the same subsystem concept they started with. On the other hand it that's probably a good thing because everything needed a rebuild for SUA.

Re: The Day AppGet Died

#208
post #158

Earlier quoted context omitted.

This. Choose your side projects wisely.

or stop attaching your real identity to online identity.

If you are so ashamed of your work that you need to do it under a different name, then maybe you shouldn't be doing it?

I'm proud of the work I've done on Sonarr. If someone doesn't want to associate with me because of it, then the feeling is probably mutual.

Re: The Day AppGet Died

#209
post #47

Fuck anyone callous enough to take something as far as an onsite trip with the pretense of a job and then just ghost them. I can't think of a much clearer way to show that much disrespect of someone and their time. And that's just the tip of the iceberg in this case. Remember things like this whenever you see the "microsoft <3 linux" slogan and the rest of the PR facade people are all too willing to swallow.

This exact thing happens all the time. And not just Microsoft. Usually you sign something that prohibits you from talking about the meetings, though.

Can confirm.

Heck, I’ve been given an interview day for a c-level position at a billion dollar company by the entire executive team and board only to never hear back from them again.

Re: The Day AppGet Died

#210
post #84

Earlier quoted context omitted.

Reminds me of: https://twitter.com/mxcl/status/608682016205344768?lang=en How exactly could a PM interview process (which is just asking you to walk through a bunch of design scenarios) give a stronger hiring signal than having developed a product the company wanted to acqui-hire? Honestly somewhat insulting that they made him go through a full external interview loop. At most it should have been some informal chats…

> Honestly somewhat insulting that they made him go through a full external interview loop. Wait, what? So if someone is a "name brand" celebrity, they should get to jump the queue and coast by with an "informal chat?" How is that fair? I don't care if I'm interviewing John Carmack, he's getting the same evaluation process I would give to any other senior candidate. Software Engineering's got enough problems with int…

I find it unlikely that even large companies put their superstar famous hires through the same hiring process.
Post reply on HN