27 ms·
The Day AppGet Died
- lostmsu 6y agoThat is exactly why I am not open sourcing my .NET bindings for TensorFlow.
- Wowfunhappy 6y agoI don't know the details of your project, but what if you open sourced under the GPL? I feels as though the world has soured on the GPL in recent years, but whenever I see this type of sentiment—that open sourcing work is just a gift from small developers to big tech companies, or something thereabouts—I think, wouldn't the GPL solve that problem? Sure, big companies can still use GPL'd code, but they're forced to give back as much as they take, which is exactly the outcome you want. (This doesn't necessarily apply to the situation with AppGet, however.)
- bluGill 6y agoBig companies are more likely to give back to non gpl code in my experience. The gpl scares them enough that when they use it they isolate it carefully so they don't have to make changes. Non gpl code (depending on license terms of course) get embedded where it is easier to need changes and then a desire to keep up with some other feature means they contribute back. Of course either way they are a business and will be careful. Their core business will not be contributed.
- rusticpenn 6y agoDual licensing helps. AGPL or Paid licence.
- SeeTheTruth 6y agoSo it's not worth it. Why be less careful than companies in the hope they will be good citizens, when it's easier to be careful and not have to hope?
- lostmsu 6y agoThat would not have helped MongoDB. I considered their new license, but it seemed tailored to their specifics. So maybe more research is required. Perhaps a variant of CC-BY NC would be better, but it is not tailored to code.
- colejohnson66 6y agoWhat’s wrong with AGPL?
- lostmsu 6y agoAFAIK AGPL permits linking without disclosing linked code like LGPL does. Meaning they can still distribute it as their own, train models and serve them with a simpler framework. Just can't build services powered directly by it.
- leonidasv 6y agoAGPL is as strict as GPL. It's just that GPL allows you to modify the source, serve them as a web application and not have to disclose the code. AGPL addresses that by putting code distributed as a web application in the same category as compiled code.
- hnick 6y agoIf my web server calls out to AGPL software (such as executing a transform on a PDF using Ghostscript) as an external binary is this covered even though the AGPL code is not directly compiled, linked or modified? I'd assume so otherwise it would be a very easy loophole and code could be firewalled into separate modules but I'm not sure what exact language covers this in the license.
- chii 6y agoIt's untested in court. GCC is written specifically to prevent this sort of firewalling of the compiler to prevent it from being plugged into another piece of software and avoid GPL requirements.
- na85 6y agoBy 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 https://www.gnu.org/philosophy/enforcing-gpl.html
- colejohnson66 6y agoThe GPL has been used successfully in courts of law. It’s not common as most violators just open source when called out, or settle when sued, but it has worked before. A famous example is D-Link using the Linux kernel in their routers. After a lawsuit in Germany, D-Link had to release their changes.[0] I don’t understand this idea that a license that the author willingly released his code under is unenforceable, but EULAs are? [0]: https://web.archive.org/web/20141007073104/http://gpl-violations.org/news/20060922-dlink-judgement_frankfurt.html https://web.archive.org/web/20141007073104/http://gpl-violat...
- tracker1 6y agoOf course with all/most US routers generally taking only signed ROMs, it's mostly useless to even have the code. I wish they'd just create something closer to tomato than the flashy, less useful interfaces.
- colejohnson66 6y agoThat problem is called TiVoization. It’s addressed with the 3rd version of the GPL. Sadly, Linus is adamantly against that clause.
- chii 6y ago> Linus is adamantly against that clause. oh i didnt know he was adamant against the clause - i thought that he didn't want to force it upon the many existing users of linux.
- solarkraft 6y agoHow much will that really change the likelihood of MS reimplementing it? They didn't take any of the AppGet code, just the ideas.
- colejohnson66 6y agoDepending on who you ask, ideas are still protected by intellectual property laws. Patents are a good example.
- lostmsu 6y agoThey might. But it is not as simple as WinGet. It would take a team or two a couple of years to reimplement. ML.NET is 2 years old now, still has very limited deep learning capabilities, and is barely visible in trend graphs. While they would be doing that, Azure will continue to lag behind (still does not even offer T4) on GPU offerings in comparison to AWS and GCP, because there's no compelling reason to run custom deep learning workloads on Azure. Azure is loosing $$$ millions of potential revenue to that. It would be a totally different story if .NET folks would get full TensorFlow and/or PyTorch in place of partial ports available now.
- WrtCdEvrydy 6y agoI wonder if one day we'll know of all the stories of people who got wined-dined-fucked by the large corporations who then release their own version of an existing product.
- banana_giraffe 6y agoI doubt it. I've hinted at in comments here in the past, but I have one such story. It's a footnote, at best, in MS's history, and a thing for a now-dead product, but they turned what I thought was a cool product into their own thing then disappeared it through internal MS politics. I don't tell the story in any details since I don't want those details getting back to the real me and having a negative impact on my career for whatever reason.
- solarkraft 6y agoHow could a gigantic corporation stealing your idea be seen as negative?
- colejohnson66 6y agoThe word “stealing” is a big hint
- FeepingCreature 6y agoHe means "seen as a black mark for you", not for the company.
- theIV 6y agoI don’t think it has to do with the corporation that did the stealing but more other corporations that might infer things from the retelling. Plenty of other corporations, of varying sizes, want to steal ideas. Comments on the internet can be interpreted in a myriad ways.
- dmix 6y agoVCs and even incubators do this all the time. It's one of their primary jobs to fish for information under the guise of helping you.
- MikusR 6y agoThe title of this should really be changed to the more descriptive subtitle: "The story of how Microsoft embraced and then killed AppGet."
- boromi 6y agoNot really. Afterall his AppGet package was open source....
- neatze 6y agoWhat point exactly are you trying to make ?
- chii 6y agoThe post was trying to imply that because the project was open source, it's a free-for-all for microsoft to just take and modify for their own needs. And that is exactly what happened.
- boromi 6y agoHonestly the tech innovation of AppGet while good, isn't something groundbreaking. Manifests have been used by other package managers in the past. Yes it's stinks he didn't get more credit, but IMO it's blown out of proportion.
- 3ycombinator 6y agoMicrosoft shill
- boromi 6y agoDid you spend time to look at the architecture he created with AppGet?
- ralphstodomingo 6y ago
- ak39 6y agoMan, this hurt to read. Keivan’s response is the right one. But I wonder if the arrangements and outcome would have been different had AppGet been closed source. This is just not cricket from team Microsoft.
- pdonis 6y ago> I wonder if the arrangements and outcome would have been different had AppGet been closed source. All of the Windows apps that MS did this to back in the 1990s were closed source. Didn't help. MS has more than enough horsepower to just reverse engineer whatever they can't get the source code for if they care enough about the features.
- lostmsu 6y agoI don't think so. There have been quite a few larger products, where Microsoft failed spectacularly.
- pdonis 6y ago> There have been quite a few larger products, where Microsoft failed spectacularly. Sure, but not because of failure to reverse engineer someone else's product.
- lostmsu 6y agoRight. That was the point: it is not enough to just understand how something was made. You have to be able to recreate it too. And building a similar system in just a bit different way to avoid potential copyright or patent claims is hard. If the system is complex, it is hard squared.
- pdonis 6y ago> it is not enough to just understand how something was made. You have to be able to recreate it too I meant to include both in "reverse engineering". What I was trying to say was that the large products where MS has failed spectacularly don't seem to me to be products from some other company that they reverse engineered. They seem to me to be products MS thought up itself. MS is better at co-opting ideas invented by others than at inventing its own.
- draw_down 6y agoMicrosoft is really good at copying. I mean this in as value-neutral a way as possible.
- solarkraft 6y agoAre they also good at deciding when to copy? They could just have taken and possibly improved AppGet's code.
- mrtweetyhack 6y agoThere's a reason they bought Github, to get at all the free code
- ASalazarMX 6y agoWe can find comfort in the thought that they're not a Chinese company, whose copying kills kittens and freedom.
- draw_down 6y agoAh, of course. Terrible when the Chinese do it, just terrible.
- kasabali 6y agoI'm sorry to hear that. When I compared various package managers few months ago I liked AppGet most. What's saddening is winget doesn't even do half of what's appget is capable of right now.
- pavlov 6y agoThe story reminds me of Andy Hertzfeld’s Switcher: https://www.folklore.org/StoryView.py?project=Macintosh&story=Switcher.txt https://www.folklore.org/StoryView.py?project=Macintosh&stor... The difference is that, in 1984, Bill Gates immediately offered $40k and Steve Jobs offered $100k for plugging a hole in their operating system. In 2020, Microsoft just strings you along on vague promises while they simultaneously rip you off.
- endgame 6y agoReminds me of Stacker and Doublespace, back in the MS-DOS 6.0 days.
- yjftsjthsd-h 6y agoI love how those stories of the early years are so different from what I think of looking at companies today - > Jeff picked me up at the airport, and we drove to Microsoft's main building where we were joined by Neil Konzen, a talented 23 year old who was Microsoft's main systems programmer on the Macintosh. I knew Neil from his days as an early Apple II hobbyist, when we collaborated on adding features to an assembly language development system when he was only 16. Just... "Microsoft's main systems programmer on the Macintosh" is such a weird sentence to read today. On the other hand, Microsoft also shipped Xenix, a full-on licensed Unix™ OS before they shipped DOS.
- pavlov 6y agoMicrosoft is still the largest Mac software vendor, and they are again in the Unix distribution business with WSL. The more things change, I guess...?
- nordsieck 6y ago> they are again in the Unix distribution business with WSL. For anyone who doesn't get this reference: https://en.wikipedia.org/wiki/Xenix https://en.wikipedia.org/wiki/Xenix https://en.wikipedia.org/wiki/Windows_Services_for_UNIX https://en.wikipedia.org/wiki/Windows_Services_for_UNIX
- fraggle222 6y agoNot sure how MSFT usually handles it, but when I was acqui-hired (by a different large tech company, not quite on MSFT scale, but no trifle) I dealt almost exclusively with a person from Business Development. Maybe it is a bad sign that they had you discussing with people in their engineering group directly. Sounds like they were gathering data from you with no real plan to acquire. Then again every company may do it differently. For me, there were some questions about my technology, but not a lot. Mostly we agreed on terms, and then they came up with a 40 page contract :) (the bus-dev guy said they don't really treat a small acquisition like mine that much differently than a larger acquisition in terms of contract verbiage). I had my lawyers (no I did not have any before this offer), review it. But overall I felt that someone, who later I'm pretty sure turned out to be the CEO, had told their Business Development guy, just acquire this thing (and bring him along if you can), so they just went about doing that and it came out ok.
- lostmsu 6y agoOut of curiosity, how long the process took until the deal was signed?
- fraggle222 6y agoI had to go back and look it was a while back, it took longer than I remembered it. The initial reach out was in May 2011. I had some initial conversation with them in May and June, sent them some overview of the company, etc. Then didn't hear back for a while. In December 2011 conversations started back up. By then the company had actually launched a product where they could see my business being useful. I sent them some small amount of data as a sample. I had actually proposed a simpler lower cost proposal of them just purchasing the data they wanted and not the business or acquiring me to work there. Anyway sometime at beginning of Feb 2012, things started to move faster and then it was done by beginning of March 2012. So in my mind/memory it was really January 2012 to beginning of March but really started in May 2011.
- haltingproblem 6y agoThanks for sharing the timeline. These things take far longer than anyone realizes.
- sneak 6y agoWhen you release free (as in freedom) software, you are not entitled to revenue sharing when people use or modify that software, or if people use the ideas in that software to make new, from-scratch software. I think Microsoft is a terrible organization and will rejoice the day they finally cease to exist as a concern, but they didn’t do anything wrong here. PHP didn’t “rip off” Perl, nor did CoffeeScript “rip off” ruby. All the other PoW or PoS blockchains didn’t “rip off” Satoshi. He needs to stop seeing ideas and concepts as “his” that are property that can be stolen. Why should they acquihire when they can just reimplement? Ideas aren’t property, and if you have a good idea, and someone else takes it and runs with it and makes software used by millions that works better than if you hadn’t had that idea, that is the system working as intended, and, ultimately, his ideas, now published and infecting the world, being writ large and used by humans. I’m not some corporate apologist, but he should be proud. (He also probably should have, back when, started a company designed to be digestible that they could have acquired, if he wanted to participate financially, like MySQL or RedHat did.)
- RandallBrown 6y agoTaking someone all the way through the interview process, then ghosting them, is doing something wrong. Add in the fact that they had planned on buying his app outright told him they would hire him instead to speed up the process, and it's an especially crummy thing to do.
- sneak 6y agoI’m not sure I agree with that. No news is the equivalent of all other times: no deal/no hire. I think the game theoretic optimal choice from a liability standpoint is to simply stop sending further messages if you decide not to do business with someone, especially given all of the current litigation-happy people there are out there these days. (Even if you win a suit, you lose lots of money.) It avoids the possibility of obsessive types getting agitated over an explicit rejection, et c. Anyone clever will see ghosting for what it plainly is: an explicit rejection. It’s just business, not some trusted friend ghosting you on lunch plans and not calling. This is how business works, and it’s not rude, it’s just the protocol.
- ReverseCold 6y agoReminds me of this scene from Silicon Valley (HBO): https://www.youtube.com/watch?v=JlwwVuSUUfc https://www.youtube.com/watch?v=JlwwVuSUUfc
- henry_bone 6y agoDefinitely a classic brainrape.
- epinephrinios 6y agoCame here to say this.
- apetresc 6y agoI 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.
- deleted 6y ago[deleted]
- person_of_color 6y agoThis. Choose your side projects wisely.
- ponker 6y agoSo that you don’t ruin your chances of being not ghosted by a company you barely want to work for.
- somebrody 6y agoThis Choose your fucks wisely.
- deleted 6y ago[deleted]
- kayone 6y agoI really doubt it was it. Sonarr was one of the topics we talked about during the first meeting at Microsoft Vancouver. Even if that was the case, I have no regrets.
- person_of_color 6y agoI would say engineers have a different perspective than upper management.
- throwaway2048 6y ago
- tannerbrockwell 6y agoMicrosoft 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.
- an_opabinia 6y agoAppGet is an open source program. Besides, if Microsoft was interested in stealing it, he’d be interviewed at Microsoft Shanghai.
- kayone 6y agosee my comment here, https://news.ycombinator.com/item?id=23332582 https://news.ycombinator.com/item?id=23332582
- deleted 6y ago[deleted]
- babesh 6y agoYou mean you have never been part of an interview or supposed acquihire were you were brain picked? That’s happened to me at least five times already. There is far more to things than code. Examples: what is your ARPU, why didn’t you do it this way, how many bytes per unit time can you upload this way, where do you see the market going, who is still at the company, what do you think of this type of market?
- jasonhansel 6y agohttps://en.wikipedia.org/wiki/Embrace,_extend,_and_extinguish https://en.wikipedia.org/wiki/Embrace,_extend,_and_extinguis...
- specialist 6y agoI'd require earnest money at the outset. After Microsoft flirted with acquiring Intuit, then shortly thereafter released Money to compete directly with Quicken, I assume all due diligence is just a way to hoover up intel. To inform a buy vs build decision. To better validate market assumptions. To identify key contributors and poach them. Whatever. No earnest money? Fine. They clearly were going to drain my blood and powder my bones. Their prerogative. But they can proceed to kill me and my product without my help.
- benatkin 6y agoI don't want to support this company. What are good alternatives to GitHub, TypeScript, npm, and Visual Studio Code (besides Atom)?
- FridgeSeal 6y ago>GitHub Github I guess? > TypeScript, npm, I don't know if you'll be able to avoid NPM, but _maybe_ you could try ReasonML if you're doing frontend stuff with TS? Don't really know tbh > Visual Studio Code (besides Atom)? Sublime Text 3 with plugins for general stuff, one of the JetBrains IDE's for more language specific work if so desired.
- willcipriano 6y ago+1 for jetbrains. I prefer webstorm to visual studio myself and the licensing scheme is very fair.
- leonidasv 6y agoReasonML is a pretty decent choice. Small learning curve, JS interop, fast compilation, functional goodies. Plus a thing called "Structural typing" that gives you the flexibility of dynamic typing without losing the guarantees from static typing.
- FridgeSeal 6y agoPlus, if they are doing front-end stuff, it's my understanding that ReasonML will also output native code, which should theoretically go a long way to making a OS-native app significantly easier right?
- leonidasv 6y agoNot really, most of the time you're probably interacting with the DOM, which is bound to the browser environment. Unless you use some framework that also works with native widgets or similar components, you're not getting much advantage.
- WesolyKubeczek 6y ago1. Release some code under a permissive license 2. Start complaining when companies exercise precisely the rights you have given them
- 1f60c 6y agoYou’re putting words in the author’s mouth, because that doesn’t seem like the problem. The problem was “the slow and dreadful communication speed” and “the total radio silence at the end”, and: > [T]he […] announcement. AppGet, which is objectively where most ideas for WinGet came from, was only mentioned as another package manager that just happened to exist; While other package managers that WinGet shares very little with were mentioned and explained much more deliberately.
- draw_down 6y agoCome on
- marcinzm 6y agoThe fact that you’re allowed to do something doesn’t mean you’re not a dick for doing so. Nor does it mean you can’t be called out for being a dick.
- Phylter 6y agoThe only complaint I see is the lack of attribution, which is something that is pretty mandatory for open source projects. He's very clear about the situation and that he didn't expect more than he got except for attribution. Did you even read the article?
- mr_toad 6y agoYou could argue that these sort of corporate shenanigans are a case for continuing to maintain an independent trusted alternative package manager.
- lame88 6y agoFuck 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.
- foobarbazetc 6y agoThis exact thing happens all the time. And not just Microsoft. Usually you sign something that prohibits you from talking about the meetings, though.
- 5etho 6y agoLol i thought it was a 4chan joke: Company [1] is not bad because every company do so.not just micro$oft 1 source: I work in the company
- godzillabrennus 6y agoCan 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.
- foobarbazetc 6y agoYeah, I speak from personal experience. Years later I met one of the people who screwed me over — they’d left that company by then — and they apologized.
- kissgyorgy 6y ago"The Day Microsoft stole my work I done for free on AppGet" would be a more accurate title...
- kayone 6y agoAuthor 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 project. How it actually works. If I were the patenting type, this would be the thing you would patent. ps. I don't regret not patenting anything. And I don't mean the general concept of package/app managers, they have been done a hundred times. If you look at similar projects across OSes, Homebrew, Chocolaty, Scoop, ninite etc; you'll see they all do it in their own way. However, WinGet works pretty much identical to the way AppGet works. Do you want to know how Microsoft WinGet works? go read the article (https://keivan.io/appget-what-chocolatey-wasnt/ https://keivan.io/appget-what-chocolatey-wasnt/) I wrote 2 years ago about how AppGet works. I'm not even upset they copied me. To me, that's a validation of how sound my idea was. What upsets me is how no credit was given.
- 13of40 6y agoCan you go into more detail about which features you believe were copied?
- deleted 6y ago[deleted]
- ahmedalsudani 6y agoFrom the article: > Do you want to know how Microsoft WinGet works? go read the article I wrote 2 years ago about how AppGet works.
- 13of40 6y agoThis is very unhelpful - I'm not really in a position to code review Microsoft's implementation and compare it to this document. I was hoping for something more like some high level details from the author of AppGet.
- alpb 6y agoThere 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 they run Mac App Store to begin with). When the author said “Microsoft would hire me, AppGet would come with me, and they would decide if they wanted to rename it something else” , I can immediately tell that’s not how you do OSS. That would be betraying to your users and maintainers. Did Microsoft ask Nat Friedman and Miguel de Icaza to bring Mono with them to kill/rename it? No, that’s not what happened. And thats how significant open source projects/communities should work; not controlled by a single person.
- kayone 6y agoJust 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.
- a-nikolaev 6y agoNot everyone is able or willing to develop large-scale open-source community/project.. Also, mono is a much large and more significant project that runs on Linux, not a Windows app.
- moron4hire 6y agoMono also runs on Windows
- comex 6y ago> Did Microsoft ask Nat Friedman and Miguel de Icaza to bring Mono with them to kill/rename it? No, that’s not what happened. Visual Studio for Mac is sort of a renamed version of MonoDevelop...
- jonhohle 6y ago
- lukeschlather 6y agoThe really sad thing is that I still don't think Microsoft has actually solved the package manager problem in any meaningful way. WinGet feels like just yet another subtly incompatible package standard. I would say Microsoft should buy Chocolatey but they would probably just ruin it. (Not to say this is a uniquely Microsoft problem; it's reminiscent of the Pipenv/Poetry/virtualenv... mess in the Python community.)
- ryan29 6y agoI'm convinced the sole purpose of some open source projects are to be good enough to prevent other open source projects from filling the void, but bad enough to keep from competing with vested commercial interests. This might just be one of those cases. Why would Microsoft want to invest in another distribution platform when they already have the Microsoft Store where they can do whatever they want? Sure, WinGet has an MIT license, but that doesn't mean anything. The only important thing is who gets to commit to the manifest(s) on the master branch. That's Microsoft. They own it. They control it. They curate it. They decide who gets to distribute via it. I'd bet money they'll tie it in to Azure somehow at some point.
- jpalomaki 6y agoMicrosoft is likely looking for a solution that would allow easy distribution of software in enterprise context without having to repackage it. Having a widely accepted and used package format would solve that. You could just pick the package for notepad++ and others and push them to workstations via Intune.
- throwaway2048 6y agoThey already have MSI though?
- corty 6y agoThere were attempts, but never any followthrough. Even MS doesn't distribute all of its software as MSI.
- jasonhansel 6y agoThis is why it's important to license FOSS projects under the (A)GPL, rather than the MIT license. It makes it far less profitable for companies to steal your ideas/code, and ensures that anything based on your work will put users first.
- bad_user 6y ago(A)GPL doesn't protect ideas. Patents do that.
- shp0ngle 6y agoThey didn’t copy the code, just the APIs and ideas. In another words, if ideas were copyrighted, GNU/Linux wouldn’t exist.
- chii 6y agoTheir lawyers will have a hard time justifying that none of the original source was used to create their new win-get project, given that the author of appget has met with the engineering team directly. So if it were GPL, microsoft would likely need to license their new winget project under GPL, which would be a win/win for open source.
- throw_m239339 6y ago> Their lawyers will have a hard time justifying that none of the original source was used to create their new win-get project, given that the author of appget has met with the engineering team directly. Exactly
- colejohnson66 6y agoWell, as the law stands now, due to Google v Oracle, APIs are copyrighted. Hopefully the Supreme Court will fix that in the coming months (they’ve agreed to hear the case), but, as of now, that’s the law.
- allenu 6y agoThis 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".
- scotty79 6y ago> some higher ups decided no, they don't need to hire you Total misjudgment on their part. Thanks to this one HN post they already lost in terms of developer good will way more than his potential salary would be. Every time anyone who uses WinGet, who read this, will think 'oh, yeah, that's the tool that Microsoft build their version of behind original author's back, while stringing him and ghosting for few months".
- mikekchar 6y agoRealistically, though, a year from now nobody will care. I mean, I started in this industry in the "MS is outright evil" era. How many people did they screw over? If I remember correctly, there was even a guy who was owed a pile of stock/stock options and when he got cancer they suddenly went missing (no need to pay the dead guy!). Day by day, year by year, these misdeeds are seen as irrelevant. MS is a different company these days (almost literally). Should we hold them accountable for their past sins forever? (I have a friend who still refuses to buy products from Nestle given their ancient "poison in baby formula is OK as long as it saves us money" stance. That's older than I am!) In reality, these kinds of antics just don't hurt companies significantly -- even ridiculously horrible things that are arguably crimes against humanity (have I invoked Godwin's law?) In comparison to some of the incredibly awful things companies do (and get away with), this is minor to the point of not even being a footnote in the annals of evil (note to self: don't google that term to check the spelling...). However, there will be a few of us who will be reminded of why we don't do business with MS (and hence will have no need of WinGet). It won't make any difference, but it will be there.
- LordHumungous 6y agoIs appget dead yet? Is the windows solution that much better?
- DanielBMarkham 6y agoLet us suppose a world where there are 17 computer programs we need. apt-get is one of them. Great program! It has done the job we've needed for decades! Millions of people are happy. Is there an ethical reason that should change?
- one2know 6y agoMicrosoft is the king of fake interviews. Absolute snakes. Netflix too. Funny how when you don't work for a competitor no one wants to talk to you, then you work for a competitor or are a competitor and the VP's want to interview you. Look, people, don't waste anyone's time unless you are going to HIRE someone. If you have a product that a big tech company is interested in, acquisition is the only path you should be considering and you should get help. Wasn't there an article by a hacker news founder which basically said: don't talk to big companies until you are ready to sell, even then get help.
- shp0ngle 6y agoIn comparison, Apple hosted MacPorts, an early OS X package manager, and started to be involved in it directly. (nowadays MacPorts is not really necessary with Homebrew around, but that’s another thing)
- grzm 6y agoHomebrew is recapitulating all of the work that previous package managers have done, while making choices like analytics and stomping on /usr/local by default that others wouldn't consider. I think there's still a place for MacPorts.
- shp0ngle 6y agoI honestly really like how HomeBrew doesn't require "sudo" for anything. Random stuff I download from internet should not require system permissions to do anything they want. That part of HB design is what sells it for me.
- saagarjha 6y agoThings you install system-wide in a folder designated as such should not really be done so by a package manager that makes insecure choices on how it installs software and maintains permissions on that directory.
- harry8 6y agoRe-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.
- chii 6y agoYou 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.
- harry8 6y agoAbsolutely they keep whatever they took under the license they took it. Obviously. And they better have that well documented. Legal might have something to say about it, for example. It gives then a headache and it tells them you don't like what they did.
- Dayshine 6y agoYou 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.
- throw_m239339 6y agoYep, this is why GPL exist. "But corporations hate GPL" as I can hear there often, well tough luck… GPL is about the rights of the users, not corporations. Another exemple of why open source projects should adopt GPL or AGPL, nothing less.
- scotty79 6y agoIsn't this completely usual corporate behavior? Even if the little guys building stuff make attempts to do the right thing, like contact and include people from outside who made the thing they are building upon, then at some level, at some stage, the arrangement gets stalled into oblivion to the point that the thing is already done and nothing can be handled gracefully anymore.
- dzonga 6y agoop, was done dirty. classic move, even SV had an episode on this kinda business. feign, an acquire-hire. and pick the team's brains out. then launch competing product. I think PG had another essay on this too, never talk to business dev folks
- deleted 6y ago[deleted]
- ijidak 6y agoKeivan 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.)
- akdor1154 6y agoI am interested (and kind of depressed) to think - is there actually a legally defensible upper hand that exists here?
- chx 6y agoIf WinGet contains AppGet code and they didn't credit him then yes, absolutely, moral rights in copyright (attribution, right of association, integrity) cannot be transferred during the lifetime of the owner and yes MSFT can be sued for breaching them. It is extremely likely the penalties meted out by a judge wouldn't cover the costs of a lawyer. Not that anything like this would ever see a courtroom, MS will offer a settlement which in this case will be on the magnitude they gave to Mike Rowe for MikeRoweSoft.com (which was an xbox and some travel vouchers and such). If they stole his unpatented ideas then there's nothing.
- panchtatvam 6y agoThis is the Embrace, extend, and extinguish policy of Microsoft. I just hate how these corporates deal with talent. To them it is nothing more than a profit to make.
- perlgeek 6y agoI'm somewhat reminded of https://en.wikipedia.org/wiki/Embrace,_extend,_and_extinguish https://en.wikipedia.org/wiki/Embrace,_extend,_and_extinguis... I know it wasn't the exact same playbook being used, but I think from the author's perspective, it very much feels like it.
- AHappyCamper 6y agoIt still stings to be treated like that. Especially when you acted in good faith at all times with MS. Sorry this happened to you buds.
- canibal57 6y agoKeep your ear to the grindstone, bud... https://youtu.be/OHSYWIAAY2o https://youtu.be/OHSYWIAAY2o
- AnonC 6y agoI can’t imagine how deeply upset you must feel over this. > I didn’t even have to explain to her how the core mechanics, terminology, the manifest format and structure, even the package repository’s folder structure, are very inspired by AppGet. I read “inspired” as “blatantly copied”. Not shocked at this from Microsoft. But not giving due credit is just a rip off. Seems like Andrew and whoever else corresponded with you were arm twisted by jerks (or had more jerks in their teams). If anyone in the Winget team is reading this, your organization sucks. It seems to be showing signs of Microsoft from the ‘90s.
- deleted 6y ago[deleted]
- de_watcher 6y agoThey've Bukkited you like Mojang/MS did.
- smcl 6y agoEvery time I see the “Microsoft <3 open source” stuff I get really suspicious, and this kinda confirms that I’m right to be. I’m grateful of their more open culture these days (dotnet alone is a big achievement) ... but I feel like there’s been a number of incidents like these which snap me back to reality and remind me they’re really just paying lip service to the idea and don’t truly buy into open source.
- globular-toast 6y agoMicrosoft is a public traded company. You can safely assume that anything they do is really about generating value for shareholders. Of course they don't "love open source". But they probably love what it does for them (e.g. enable them to run Azure).
- throw_m239339 6y agoSo much for the "I love the new Microsoft" people here… same as the whole Microsoft, doesn't even have the decency to credit people where credit is due… Of course, nothing illegal here, but this is borderline plagiarism… at least pay the guy, or donate to his foundation or something… Seems like Microsoft owning GitHub thinks all the code on GitHub belongs to Microsoft…
- madc 6y agoThis is who owns GitHub now.
- rStar 6y agoFuck em
- julienfr112 6y agothe Bad PR involved here largely offset what a good bonus to kayone whould have been. If it move the needle, say between Azure and Gcloud, on 10% of the thousand of read of this post, MS could end up losing millions of dollars a year.
- 1propionyl 6y agoI don't think there's any need to blame Microsoft here. It's not like they've ever done something like this before. If they had, surely they'd have learned from the backlash.
- deleted 6y ago[deleted]
- dusted 6y agoSounds like Microsoft. Sorry you had to try that personally, I'm certain it's stressful and frustrating, thank you for writing about it and sharing.
- onemoresoop 6y agoThis is really sad, not only did they copy your idea, not paid you anything (yeah, some kind of azure credit is not really costing them anything) nor gave you credit, they wasted your time and gave you a humiliating silent treatment. At a smaller company I tend to think that wouldn’t have happened but Im not sure to be honest. I hope that you get the credit and end up in the place you deserve to be. I wonder if Andrew is an a-hole or he really just couldnt do anything about it, it is possible that they didn’t want to remunerate you for legal reasons, in the sense that you could have asked for more later on. But no credit? I think Andrew may be as I first thought
- pfortuny 6y agoAfter reading the second e-mail it is clear that they are trying to do something "official" and that their interest in the specific person is low (to say it mildly). Full of "going-forward" and similar corporate-speak. DANGER DANGER DANGER: when someone loses natural language, he is no longer speaking for himself. What a pitiful world we live in.
- dandare 6y agoI wish someone would write a serious corporate-speak dictionary, list the most used phrases and what they usually mean, explain different levels of formality etc.
- corty 6y agoSeconded. As a foreigner it is even harder to recognize such phrases for what they are and interpret them correctly.
- sergeykish 6y ago> As you know we are big fans of package managers on Windows and we are looking to do more in that space. that part looked wrong
- MrGilbert 6y agoThis is the reason I'm hesitant to open source an idea I have to build as a SaaS. I'm a big proponent of self-hosting, so I'd like to offer my SaaS for self-hosting to anyone that wants to. There is always a risk of <Big Megacorp> might come around, think "oh, that's neat!", and away they are with a marketing budget miles higher than mine.
- scoutt 6y agoYou have been Microsoft'd.
- nailer 6y agoDupe of https://news.ycombinator.com/item?id=23305068 https://news.ycombinator.com/item?id=23305068
- kristofarkas 6y agoIt's understandable that everybody is blaming Microsoft for the way this was handled. But let's remember that we are only seeing one side of this story, we don't know what really went on from Microsoft and the team's side there.
- kkapelon 6y agoIt doesn't really matter. What ever happened on the Microsoft side should be communicated to him. The fact that they ghosted him after flying him on site and milking him for information looks bad anyway. What scenario do you have in mind that would make Microsoft look in a positive way in this incident?
- hasanalikhattak 6y agoIt's really shameful how a prestigious service like AppGet for neglected Windows users got screwed by Microsoft. My sincere thoughts are with kayone and AppGet.
- wwwigham 6y agoI feel bad for the OP for getting ghosted by the Microsoft hiring process, I'd at least want a prompt response of _some_ kind; but the package manager features OP says are "copied" are common to cocoapods, homebrew, and others... Winget is certainly not the first, and probably won't be the last package manager to take that tack, so I don't find that appeal terribly compelling (The bad hiring process though... That's annoying). If winget is a "copy" of appget, it doesn't look like a very _good_ or _complete_ one at a glance, so the author could probably keep at appget, what with the publicity; winget doesn't even uninstall or upgrade packages (yet, at least), so it's just a glorified search bar strapped to msiexec (not to lessen anyone's effort or plans, software takes a lot of time and effort to build). If the JS package manager scene has taught me anything, it's that so long as one another's manifests/registries are readable, developers will happily try multiple programs which actually do the managing, and, to some degree, a little competition is what actually makes things gradually improve. I, at least, hadn't heard of appget prior to today. (Just chocolatey and oneget, both of which I'd used, both of which are likewise "invalidated" by winget, but persist regardless.) But I can only reasonably consider it if its primary maintainer reconsiders its "dead" status.
- christopoulos 6y agoThis is why I personally am very reluctant to the sharing of well founded ideas on platforms such as github, in hackathons, in competitions, in recorded speeches etc. How unlikely it may seem, this is a great example that ideas with traction do get picked up and copied, and the originator screwed over. I honestly sometimes feel as if the openness is pushed and saluted, but with the ulterior motive to skim for ideas. Edit: corrected autocorrect
- brnt 6y agoOn a tangentially related note: how did getdeb.net die? Used to use this a decade ago, but then suddenly the domain went blank and now is taken over by a squatter I see.
- _rrnv 6y agoSeriously, business never was and never will be a nice place. For every company in Silicon Valley there's a story about a dickmove, both in startups and corporations. Yes, Microsoft screwed you over. Capitalise on the drama buzz and move on.
- j-pb 6y agoWhelp there goes any chance I'm going to consider any M$ products to replace my Macbook as a main dev and work machine. Looks like the only viable remaining ecosystem is a linux laptop...
- helsinkiandrew 6y agoIf Microsoft is serious about supporting open source then this is the kind of story that it needs to stop happening. It may be perfectly legal to come out with their own version of AppGet, to base it on AppGet, and give it a name that is very close to AppGet, and if the developer wasn't a fit for Microsoft then they don't have to hire him. But behaving in this way is like biting the hand that feeds you in terms of open source they come out sounding like a*oles. When it was clear they didn't want to do an acqui-hire one solution would be to indicate that it was possibly they were going to create their own version of the product and perhaps 'purchase' the AppGet design/concept, or pay a consultancy fee for the time the developer was being interviewed - even for a token sum.
- doublerabbit 6y ago> If Microsoft is serious about supporting open source Microsoft isn’t serious about supporting open source at all. It’s just a gimmicky ploy to get users back from Linux to Windows.
- LockAndLol 6y agoAnd it's working. Linux users are even excited about WSL, cross-platform C#, Microsoft in a VM being called Linux native, github being bought, etc. Linux users aren't more principled or anything than windows users. I'd go as far and say that people just want free stuff and some are willing to put more effort into it. We have no higher standards or morals and are no better than the windows or mac crowd.
- MaulingMonkey 6y agoIt's working both ways, fortunately. Yes, I get to use Linux tools from Windows, helping keep me on Windows. But it also means I'm more likely to build/test/fix my junk on Linux, helping me reduce my absolute and pre-existing dependency on Windows.
- a_imho 6y agotldr; new Microsoft hearting open source
- ecmascript 6y agoJust don't develop large open source stuff for large companies. It's not worth it, they will always screw you if they can. For example, make a great app for any platform and they will most likely incorporate the exact concept since it's successful. This is why you should focus on the web, publishing on your own and then they can't simply steamroll you in the same way since the platform is open.
- qball12 6y agoAaah, good old Microsoft is back!
- pgt 6y agoHey Microsoft, whenever you do this, you lose all the goodwill you've built with developers. You have put me back in a buying position where I'm now thinking: how can I cancel my paid GitHub & Azure accounts?
- UkiahSmith 6y agoNever forget, https://en.wikipedia.org/wiki/Stac_Electronics#Microsoft_lawsuit https://en.wikipedia.org/wiki/Stac_Electronics#Microsoft_law...
- jonnypotty 6y agoMate, that sucks. Sorry, fuck those dick heads. That email, meant to aswage their guilt, hey we gave _you_ knowledge of the release date, don't you feel special. Its like people pushing infront of you on the road, nearly making you crash and then thanking you. Grrrr
- ChrisMarshallNY 6y agoI 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."
- amdavidson 6y agoI believe the more common version of that term is "Sherlocked"
- ChrisMarshallNY 6y agoYou are correct.
- ChrisMarshallNY 6y agoHere's something that I think was written in the early 1990s. Shows that the leopard hasn't changed its spots much: http://www.davar.net/HUMOR/STORIES/MS-CUISN.HTM http://www.davar.net/HUMOR/STORIES/MS-CUISN.HTM
- pwdisswordfish2 6y agoPosts 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.
- olaf 6y agowhat do I learn from that? I will not talk with a Microsoft representative before they pay me at least 5000 US$ consulting fees. Never give them something for free, not one minute of my precious lifetime. They seem to me as 'friendly' as the aliens in the "Mars attacks" movie.
- chethiya 6y agoThere is an issue created in winget GitHub page suggesting to donate appget -https://github.com/microsoft/winget-cli/issues/353 https://github.com/microsoft/winget-cli/issues/353
- pixelmonkey 6y agoI've been learning a little bit about "the new Microsoft" and its new relationship with open source, and I think I get it now. MSFT is treating open source communities and free F/OSS code contributions the way they might have treated blogging and IT forums in a prior era. It's "developer community" and "power user" engagement. It's a hybrid product management and marketing function. In this particular scenario, the winget product manager views the appget author as a "Windows enthusiast" of sorts, not a competitor, a peer, or a colleague. Just a "power user persona" of the Microsoft userbase. So, when you understand this, reading the PM's email to him ahead of winget's launch makes more sense. > We give appget a call out in our blog post too since we believe there will be space for different package managers on windows. You will see our package manager is based on GitHub too but obviously with our own implementation etc. our package manager will be open source too so obviously we would welcome any contribution from you. Specifically: it's like getting called out explicitly by a forum mod, or being a frequent blog commenter who is mentioned by name in a blogger's main post. It's "an honor" to have appget explicitly mentioned in an "official" Microsoft announcement. And to have your community work "inspire" so much of winget's design! So when the PM wrote the email, he probably wasn't even thinking it would feel like trolling. He was probably thinking, "isn't it cool we are doing this 'F/OSS collaboration thing' together? How 'New Microsoft' of us!" And I can't say I blame him. Microsoft is just less smooth about their appropriation of F/OSS for marketing purposes. Other companies manage to do it without the developers noticing.
- logicalmind 6y agoIf you want to see what Microsoft thinks of open source and contributors, then all you have to do is read the license they want you to agree to before doing so: https://opensource.microsoft.com/pdf/microsoft-contribution-license-agreement.pdf https://opensource.microsoft.com/pdf/microsoft-contribution-...
- usertiljune2020 6y agoAppGet should from now on be useful for downloading and installing wild tienes Torrents
- jmgpeeters 6y agoI thought Microsoft had changed in recent years. :/
- creativecupcak3 6y agoIt amazes me how level-headed the author really is about all this. I feel like I'm a lot more upset about this than the author. And, just like him, I don't care that they "forked" the project. I'm upset of how cunning of Microsoft this whole thing feels.
- newmac 6y agoThis 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.
- 3ycombinator 6y ago>embrace extend extinguish Serve as a warning for everyone who belives the lie of “Microsoft loves open source ”
- 3ycombinator 6y agoSimp
- wazoox 6y agoTypical Microsoft. If they're interested in what you're doing, be acquired or be crushed. Microsoft loves opensource; they love linux too. Like I love mashed potatoes : well cooked, thinky crushed then with some cream on top.
- x32n23nr 6y agoIs there an open-source license that prohibits the use of software if your company's yearly revenue is higher than < X > ?
- rectang 6y agoThere is not, because that would not be compatible with one of the non-discrimination clauses of the Open Source Definition. https://opensource.org/osd https://opensource.org/osd > 5. No Discrimination Against Persons or Groups
- GordonS 6y agoI know this might be unpopular with OSS idealists, but I wonder if it might be time for a new license, or indeed if there are already (small 'o') open source licenses that would help with this sort of things. What I'm thinking of is a license almost identical to the MIT and/or Apache 2.0 license, but with a clause that prohibits mega-corps from wholesale rebranding and using your code. I have a few OSS projects myself, and help maintain a larger one, and I love the spirit of OSS, so I'm a little split on this one. But I don't really think Microsoft's actions here are truely in the spirit of OSS. Yes, the license allows it, but is it aligned with the OSS ethos? Is it "right"?
- nojs 6y agoWouldn’t that be GPL?
- GordonS 6y agoNo, that puts restrictions on everyone, which are so harsh many organisations (even startups) wouldn't touch GPL'd code with a bargepole. I was thinking more along the ideas of adding restrictions only for corporations of a certain size, or perhaps only if they intend to use it in a certain way - kind of like the licenses that exclude large cloud operators like AWS from using your work without contributing back.
- huhtenberg 6y agoNo, of course not. But the viral nature of GPL and the notion of "derived works" may be of some use here.
- Dayshine 6y ago> with a clause that prohibits mega-corps from wholesale rebranding and using your code That didn't happen in this case. They took the ideas, and took his knowledge by leading him on and interviewing him for an acqui-hire. They didn't take his code (in C#) and rewrite it in to C++.
- andrew_ 6y agoExactly why I started relicensing all of my projects under MPL-2.0. The decision followed an attempt by a webpack team member to wholesale copy a project of mine into the project without attribution or licensing (which is a separate issue). Decided then and there that I needed something more restrictive that still allowed for collaboration.
- jlengrand 6y agoMaybe @Microsoft has something in the drawers that would be interesting for OP and propose as a contingency plan? That'd be a way to make amend :)
- rashil2000 6y agoHi, just wanted to chime in and ask a question. Wouldn't MS (or any company for that matter) get in legal trouble for endorsing/crediting a developer who has a history of making software that uses/manages pirated content? The software I'm talking about is Sonarr, and it’s made by Keivan himself. I'm not aware of the legalities here, so asking.
- pojntfx 6y agoAGPL-3.0 is a great thing.
- Uhrheber 6y agoEmbrace, extend, and extinguish. Microsoft being Microsoft. Some things never change.
- jgeerts 6y agoWent to the github Microsoft package and came across this issue, posted by one of you. https://github.com/microsoft/winget-cli/issues/353 https://github.com/microsoft/winget-cli/issues/353
- jdonaldson 6y agoI was curious about hearing Microsoft's side of the story. There's an existing issue filed against the winget repo for this, if you're interested, subscribe to the issue: https://github.com/microsoft/winget-cli/issues/353 https://github.com/microsoft/winget-cli/issues/353
- TeeWEE 6y agoI had the same idea! I'm supporting this issue. Lets use github & opensource itself to ensure the Appget developers gets his fair share!
- typenil 6y agoGood to have another data point to temper my opinion of Microsoft. It had been rising lately.
- astn-austin 6y agoI don't get it. You open source something (make it public) so everyone can benefit in any way, inspiring, forking, extending, giving back, etc. Someone does so and your offended?
- astn-austin 6y agoAs far as being offended that they called it WinGet when you had a package manager called AppGet. MS already had a "package manager" called OneGet. They also have a package manager called NuGet. I don't see any issue with MS replacing OneGet with WinGet. Or why the name WinGet offends AppGet, or AptGet, or OneGet, or NuGet, etc. I think [name]Get is pretty common.
- simonblack 6y agoJust in case you weren't around in the early 1990s, what happened to you was practically identical to what happened to Stac Electronics. They had a hard-drive compression program, got into 'negotiations' with Microsoft, then nothing. A little while later, Microsoft incorporated their DoubleSpace into MSDOS. plus ça change, plus c'est la même chose