Another good reminder that Hacker News is not above assuming the worst and gathering pitchfork mobs like any other social media.
The issue looked like a mistake from the start to anyone paying attention (committed by a bot, changes were consistent with a boilerplate LICENSE file being checked in).
If someone at Microsoft wanted to steal some code, forking it on Github and then publicly documenting the history of the code in the most visible way possible would truly be the dumbest way to do it.
I would go so far as to say almost no group is, they just have different preconceptions that encourage assumptions of malice in different ways and directions.
There is no substitute for more facts about the situation, no matter how much we'd like to assume the details that aren't given.
[0] https://openprinting.github.io/cups
[1] MSFT moved attribution to NOTICE file, which is cleaner, but trips people who aren't paying attention: https://github.com/microsoft/cups/blob/main/NOTICE
The point I was trying to make that for companies like Microsoft, reaching for the pitchfork is not always a knee-jerk reaction IMHO. For all the things they have done, my initial reaction is always Oof, not again..., which is actually sad for a company of this size.
It's actually unfathomable to me for a company like Microsoft to not test these flows adequately and allowing this to happen.
For a change, I want to see a more open computing platform, a less intrusive Windows version, or a longer maintenance window for CentOS, but we all have is a brawl.
Or, shall we be stateless, and evaluate every events without any prior experience? I don't think that holds a lot of water in real world, either.
I don't think it's going to be possible to salvage the torch and pitchfork comments on this thread. For lack of a better way to put it: they're pretty dumb.
Actually, not being able to find a plausible gain in five minutes doesn't automatically clear Microsoft (or any company) in my mind. From top of my head, I can list three technologies which I find suspicious in the long run: LSP, WSL, SecureBoot.
All in all, I just don't trust Microsoft, and think about the worst of their actions first. They're the only company (ORACLE being a firm second) which evoke this reaction for me, and this their own making over the years.
Just because I don't trust a company and assume the worst of them, and telling this openly makes me a knee-jerk person, so be it.
As I said, I'm happy to be proven wrong, but I refuse to be stateless, and look every action of this company with completely neutral eyes.
Track records matter and Microsoft doesn't have a clean one. Scrutiny of companies of their size should be the norm. Maybe they would do more to improve "mistakes" if more people held them accountable in a continuous fashion.
Hardly "weasel words" when you look at the action that took place. It wouldn't be OK for you to do it and it isn't OK for a bot that Microsoft deployed incorrectly to do either.
I understand the license. Based on your response and Microsoft's attribution change I don't think you understand the argument. I won't patronize you however based on the non-response.
So, yes, nonsense issue. What am I missing?
The Microsoft STL issues are usually quite fun and entertaining, at least if you don't have to use it: https://github.com/microsoft/STL/issues/1603
The thread would have been a lot more fun if we could have spent it talking about what prompted your team to build this thingy, and bounce other people's approaches to the same problem off, and maybe share some war stories about dumb things bots have done on our behalf.
Thanks, regardless, for the information you've provided here. It's interesting.