Live data from Hacker News

The Day AppGet Died

keivan.io

401–410 of 566 posts

Re: The Day AppGet Died

#401
post #80

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

I flew to Seattle on December 5th to have a full day of interviews/meetings at Microsoft HQ. I met with four different people; three of the meetings were more like your typical interviews; the meeting with Andrew was more about what we should do once this is all over and how we would migrate AppGet’s process and infrastructure to be able to handle Microsoft’s scale. We talked about some of our options, but in general…

A friend of mine sent a resume, didn't hear anything and then got a job offer _4 months_ later. Generally I agree, not hearing anything means you didn't pass, but fuck companies and the people that do that and I don't ever want to work at one.

Re: The Day AppGet Died

#402

I have a sneaking suspicion that part of the reason for the sudden radio-silence after his on-campus interview is that someone up the chain realized he is also the creator of Sonarr and just nobody wanted to take ownership of that potential liability.

Why? From the way you were talking about Sonarr, I expected it to be something more than... a bittorrent organizer. It has nearly 6k stars on github and seems wildly popular. Why would that be taken as anything but a strong "hire this person" signal? I mean, I believe that it's possible you're correct. But this is just such a foreign "does not compute" situation to me. Is the thought process something like "Sonarr is…

Pretty easy to understand if you understand how risk-averse big corporations are, and how the image of BitTorrent has been forever polluted by "but, it's copyright infringement!".

Anything mentioning or using BitTorrent is scary for these huge companies, because it's associated with piracy.

Sure, your deploy times to your container fleet can be 70% faster, but if you're using BitTorrent, it'll be very hard to push that through leadership.

Re: The Day AppGet Died

#403
This is unfortunately not much different than MS/Github's treatment of npm. They brought npm in, had lots of conversations, and then released a competing product. In the case of npm, they went on to buy them on the cheap.

There was a lot to be annoyed with npm about, but this isn't the kind of behaviour we should reward.

Re: The Day AppGet Died

#404
post #80

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

I flew to Seattle on December 5th to have a full day of interviews/meetings at Microsoft HQ. I met with four different people; three of the meetings were more like your typical interviews; the meeting with Andrew was more about what we should do once this is all over and how we would migrate AppGet’s process and infrastructure to be able to handle Microsoft’s scale. We talked about some of our options, but in general…

Yes sometimes it means that. But if the company is desirable, knows its desirable and knows the interview means a lot to the interviewee, then its the height of arrogance and cruelty to 'ghost' them. Screw that 'just business', its not just business, its shitty behavior out of a company that has the resources to do the right thing.

Re: The Day AppGet Died

#405
post #80

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

>What upsets me is how no credit was given

Apache license requires to preserve copyright notices, did you have any?

Re: The Day AppGet Died

#406
post #80

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

I'm sorry. This does feel like a pretty shitty situation. I hope all of this attention helps connect you with some people you go on to do great things with!

Re: The Day AppGet Died

#408
post #80

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

>What upsets me is how no credit was given Apache license requires to preserve copyright notices, did you have any?

That would only apply if they copied code as opposed to architecture/concepts, no?

Re: The Day AppGet Died

#410
post #161
post #139

Re-licensee all your appget code as GPL v3. Everything about it. It might put the wind up them a little. They hate GPL. Good example of the strength of the GPL for projects you want to be open and don't want mega-corp to embrace and close. BSD, MIT etc if you're fine with that being done for the project. There are other dimensions for licensing, this is just one consideration of many in your decision.

You cannot retroactively relicense code - only new code. Microsoft can just take the last version that's not GPL. This is why if i were making an open source project, it will start off with GPLv3, with a commercial paid license if anyone wants to avoid the terms of the GPL. That gives the best of both worlds - open access to anyone, and if they want to modify, they must also be willing to contribute in some way.

You can totally rewrite your entire git history to make the entire repository GPL.

You have no obligation to continue hosting the MIT version, and you can release a new version of every commit under GPL.

Post reply on HN