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

101–110 of 566 posts

Re: The Day AppGet Died

#101

Post by kayone »

alpb wrote: post #91

There are parts of Microsoft that understand open source. Most parts of the Windows team ain’t that (exceptions apply). Reading this saddens me a lot as he clearly got screwed. But this is why any project with momentum should consider growing its community and maybe forming a foundation. For example, Homebrew and its community/infrastructure is better than and bigger than anything Apple could ever do (and we know how…

Just to be clear, I was very clear with them during our conversation that it would only happen if they committed to keeping the spirit of AppGet (which they did)

I might be wrong, but I don't think to have MS behind a project like that causing it exponentially grow was a betrail of users.

Re: The Day AppGet Died

#102

Post by giancarlostoro »

kayone wrote: 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…

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 rogue applications on their package manager.

I try to assume no bad intentions these days.

Re: The Day AppGet Died

#104

Post by na85 »

ASalazarMX wrote: post #48
na85 wrote: post #20

Earlier quoted context omitted.

By Eben Moglen's own admission[0], the GPL has never been successfully enforced in a court of law, even against criminal infringers. It seems toothless to me. A relic from a byegone era when companies cared about ethical behavior. [0] https://www.gnu.org/philosophy/enforcing-gpl.html

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 afraid of testing it in court.

(implying it has never been tested in any court)

>We do not find ourselves taking the GPL to court because no one has yet been willing to risk contesting it with us there.

(Explicitly stating it has never been tested in court)

>I have assisted free software developers other than the FSF to deal with such problems, which we have resolved—since the criminal infringer would not voluntarily desist and, in the cases I have in mind, legal technicalities prevented actual criminal prosecution of the violators—by talking to redistributors and potential customers.

And lastly, the money quote. In the cases of criminal, malicious infringement, they were not able to prosecute.

Re: The Day AppGet Died

#105

Post by ErikAugust »

kayone wrote: 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…

At this point, why not keep it going? Your story is good enough reason to keep working and build a community and/or foundation around AppGet.

Re: The Day AppGet Died

#106

Post by jasonhansel »

tannerbrockwell wrote: post #23

Microsoft pretends to want to acquire a product or software and then release their own implementation. The developer was obviously brain-picked for any implementation ideas, as stated at scale. They should have been paying a retainer, or had an offer inside of two weeks. Let this be a warning for other developers.

https://en.wikipedia.org/wiki/Embrace,_extend,_and_extinguis...

Re: The Day AppGet Died

#108

Post by allenu »

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 people (not recruiters) who reached out to you should've connected after the decision was made. They probably figured the recruiters would do their dirty work, so no need to engage.

Full disclosure: I worked at Microsoft for over a decade, so I know how slow and lumbering it can be. I bet some emails were missed and people didn't follow up because "they had a lot of other things they were tracking".

Re: The Day AppGet Died

#109

Post by imprettycool »

kayone wrote: 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…

Plus you get free PR

Re: The Day AppGet Died

#110

Post by mikerathbun »

tracker1 wrote: post #64
intern4tional wrote: post #49

Earlier quoted context omitted.

This isn't secret news, but when you interview at MS there is always a secret / hidden interviewer. This is publicly known information from Cracking the Coding interview. This person is called the as appropriate and you only meet them if you pass all the prior interviews. Per his writeup, he did not meet that person, which means that he most likely did not pass the interview. He also for some reason didn't follow up…

My understanding is when MS decides they aren't going to hire, they cut off all communication, total lot drop. Sometimes at their own campus, no feedback at all. It's really an angering experience imo. I mean, I get it from a litigious mindset, but still not very humane.

My experience while interviewing with MS is somewhat similar with respect to not hearing back after each stage. The initial phone interview was quick with what seemed like a lower level HR person who asked basic questions from a list with many mispronunciations of MS SQL technologies. I didn't hear anything for three weeks so I called them and they said, "Oh yeah. We want to schedule another phoner with the product team". A few days later I interviewed with for about an hour with two engineers and it was more inline with what I had expected. This time I sent an email the next day thanking them hoping that would at least keep me in the back of their minds. Same thing. About three weeks later I called to find out my status. "Oh yeah. We would like to fly you to Virginia for an in person interview this week". They set up my flight and hotel and I went through three interviews with different groups and left thinking, "Well that was horrible and embarrassing. They are way above anyone I had ever worked with". Same thing. Sent an email thanking them along with my expenses. About six weeks later I needed to know my status since funds were getting low. I called them up and was told I wasn't ready to work for them. But I should add them on LinkedIn to keep in touch. My self esteem was pretty shot, but I ended up with a pretty sweet job that week. I still get emails from them every once in a while when a position opens up, but three years later I still get a little anxious when those emails hit.

So yeah, their post interview stage communication seems to be the weakest part of a process I am sure I was one of hundreds going through at that time.

Post reply on HN