6 ms·

Microsoft finally gives AppGet developer the credit he deserves

47 points by theBashShell 6y ago

leetrout 6y ago
> More specifically, we failed to live up to this with Keivan and AppGet. This was the last thing that we wanted. Bullshit. Hopefully Keivan not commenting means he’s going to get more than just credit in a README and whatever it is doesn’t get locked under an NDA.
- nitinreddy88 6y ago
  How can you come to conclusion that He's looking for some compensation?
  - pavel_lishin 6y ago
    Probably from his blog post, where he was promised a job, which typically comes with some. https://keivan.io/the-day-appget-died/ https://keivan.io/the-day-appget-died/
  - leetrout 6y ago
    I’m not - it’s speculation based on the comment (linked from the article) being on an issue with the title “Donate to AppGet”
- ljm 6y ago
  > This is the last thing we wanted It's hard to believe the unironic use of that phrase in response to something they had complete control over. If they didn't want it to happen, then they had ample opportunity to do things differently to the way they actually did.
tixocloud 6y ago
I would hope that Keivan would be well compensated especially since they directly reached out in the first place. Credit in a Readme portion is the very least that he deserves. Even if the Microsoft team was only lightly influenced, the way to build a strong developer relationship community is to acknowledge someone else's expertise through proper compensation (monetary or otherwise). Besides, Microsoft can afford it!
- dilap 6y ago
  It's always hard to know how much to generalize from the general HN sentiment, but... For a company that seems to be trying really hard to win back the hearts of devs, it seems like a no-brainer to have a policy in situations such as this to give $$$ to the dev. Take it out of the marketing budget.
- nirui 6y ago
  In my opinion, "Credited in Readme" is what somebody should get when they committed an important, saver level patch for a free and open source software. Microsoft Windows however, is not that, at all. Microsoft should hire that guy which could be a better ending, but they did not. MS played this game really un-well I must say.
there_the_and 6y ago
[deleted]
- sneak 6y ago
  Isn't that what building for the Windows API is in general, though? You're enriching a platform that ultimately benefits someone who isn't you. Nobody owns POSIX.
- toyg 6y ago
  You’re not just helping MS, you’re helping millions (billions?) of their users - people who cannot afford the time (Linux) or luxury (Apple) of alternatives. Think of a world without Firefox for Windows.
merricksb 6y ago
Discussed yesterday: https://news.ycombinator.com/item?id=23377992 https://news.ycombinator.com/item?id=23377992
aasasd 6y ago
Marketing-speak is pretty strong with this product manager.
Ciantic 6y ago
Thing that bothers me in this is that Microsoft made the effort to fly Keivan to the Redmond for interviews and meetings. Why do that? Apple sherlocks it's developer base all the time, and they give very little if none of the credit to original authors of the idea. By flying the Keivan to the Redmond they gave him false hope of something, and wasted his time. Instead they should have asked about him nothing, if they weren't going to break software license doing their WinGet. It was withing their right to copy it. Worse thing is to raise false hopes and false expectations. They will surely doom any relationship, regardless if it's about product sales or personal.
wayneftw 6y ago
Nobody in any of these threads has pointed out an original idea that AppGet implemented. Looking at the list of features Keivan he was credited for, I see nothing original. Microsoft's project is written in C++, Keivans in C#. Nothing was copied. Nice witch hunt HN.
- tech-historian 6y ago
  Seems like you've captured the prevailing mindset at Microsoft that allowed this to happen in the first place. You'd be a good candidate to work there. Do you currently?
  - wayneftw 6y ago
    > Seems like you've captured the prevailing mindset at Microsoft that allowed this to happen in the first place. What's "this"? I haven't seen evidence of anything that's immoral or unethical here. Care to give a rebuttal that isn't just more of the same rhetoric?? > You'd be a good candidate to work there. Do you currently? Insinuations of shilling are such a chicken shit argument. They're also against the forum rules. Stop doing that.

47 points by theBashShell 6y ago

> More specifically, we failed to live up to this with Keivan and AppGet. This was the last thing that we wanted. Bullshit. Hopefully Keivan not commenting means he’s going to get more than just credit in a README and whatever it is doesn’t get locked under an NDA.

nitinreddy88 6y ago
How can you come to conclusion that He's looking for some compensation?
- pavel_lishin 6y ago
  Probably from his blog post, where he was promised a job, which typically comes with some. https://keivan.io/the-day-appget-died/ https://keivan.io/the-day-appget-died/
- leetrout 6y ago
  I’m not - it’s speculation based on the comment (linked from the article) being on an issue with the title “Donate to AppGet”
ljm 6y ago
> This is the last thing we wanted It's hard to believe the unironic use of that phrase in response to something they had complete control over. If they didn't want it to happen, then they had ample opportunity to do things differently to the way they actually did.

tixocloud 6y ago

I would hope that Keivan would be well compensated especially since they directly reached out in the first place. Credit in a Readme portion is the very least that he deserves. Even if the Microsoft team was only lightly influenced, the way to build a strong developer relationship community is to acknowledge someone else's expertise through proper compensation (monetary or otherwise). Besides, Microsoft can afford it!

dilap 6y ago
It's always hard to know how much to generalize from the general HN sentiment, but... For a company that seems to be trying really hard to win back the hearts of devs, it seems like a no-brainer to have a policy in situations such as this to give $$$ to the dev. Take it out of the marketing budget.
nirui 6y ago
In my opinion, "Credited in Readme" is what somebody should get when they committed an important, saver level patch for a free and open source software. Microsoft Windows however, is not that, at all. Microsoft should hire that guy which could be a better ending, but they did not. MS played this game really un-well I must say.

there_the_and 6y ago

[deleted]

sneak 6y ago
Isn't that what building for the Windows API is in general, though? You're enriching a platform that ultimately benefits someone who isn't you. Nobody owns POSIX.
toyg 6y ago
You’re not just helping MS, you’re helping millions (billions?) of their users - people who cannot afford the time (Linux) or luxury (Apple) of alternatives. Think of a world without Firefox for Windows.

merricksb 6y ago

Discussed yesterday: https://news.ycombinator.com/item?id=23377992 https://news.ycombinator.com/item?id=23377992

aasasd 6y ago

Marketing-speak is pretty strong with this product manager.

Ciantic 6y ago

Thing that bothers me in this is that Microsoft made the effort to fly Keivan to the Redmond for interviews and meetings. Why do that? Apple sherlocks it's developer base all the time, and they give very little if none of the credit to original authors of the idea. By flying the Keivan to the Redmond they gave him false hope of something, and wasted his time. Instead they should have asked about him nothing, if they weren't going to break software license doing their WinGet. It was withing their right to copy it. Worse thing is to raise false hopes and false expectations. They will surely doom any relationship, regardless if it's about product sales or personal.

wayneftw 6y ago

Nobody in any of these threads has pointed out an original idea that AppGet implemented. Looking at the list of features Keivan he was credited for, I see nothing original. Microsoft's project is written in C++, Keivans in C#. Nothing was copied. Nice witch hunt HN.

tech-historian 6y ago
Seems like you've captured the prevailing mindset at Microsoft that allowed this to happen in the first place. You'd be a good candidate to work there. Do you currently?
- wayneftw 6y ago
  > Seems like you've captured the prevailing mindset at Microsoft that allowed this to happen in the first place. What's "this"? I haven't seen evidence of anything that's immoral or unethical here. Care to give a rebuttal that isn't just more of the same rhetoric?? > You'd be a good candidate to work there. Do you currently? Insinuations of shilling are such a chicken shit argument. They're also against the forum rules. Stop doing that.