I am not a legal, so can't comment on legal things. However, I have already responded elsewhere here that this feature has nothing to do with licensing or ownership and was added for those that want the attribution. I understand the desire to see anything Microsoft as bad and evil, but we are really just trying to make a better experience.
I'll respond to the third one, thanks!
> are you interested in my opinion on (n)vim?
The first comment is three short lines. One of them is the extremely reasonable and relevant question of where else this has happened in VSCode.
And you think that the commenter is wondering about your opinion on (n)vim? That is what you think they are interested in?
Could you just, like, ignore the signature if it is distracting you from the only other line that has a question in it?
> cwebster-99 / Courtney Webster / Product Manager at @microsoft working on VS Code and GitHub Copilot!
>> No description provided.
Stop making HN a worse place for everyone by being unnecessarily hostile. (and this comment is only mildly directed at you but rather at a bunch of people in this thread)
Anyone with a bit of software experience knows it’s easy to miss things when you are doing your own tasks + context switching + giving reviews. We should exercise kindness and empathy instead of projecting evil intentions.
Funny how these "mistakes" only seem to happen in ways that align with the agenda of the supposedly non-evil corporation.
Pretty sure no one thought “let’s add a lie to every commit and hopefully no one minds. Free Marketing yay!” at Microsoft.
They might not have intentionally done this (although it's honestly not clear), but they definitely didn't care enough to prevent it because it wouldn't have been hard at all. That's my point here; which bugs slip through and which don't implicitly conveys what their priorities are. I don't think it's particularly hard to infer what story this bug tells.