Hacker News Reader

Comment by galonk | Hacker News Reader

They pretended to be fronting up but didn’t respond to anything after that. Doesn’t seem very commendable to me.

Other people aren’t your slaves. You don’t get to demand they respond immediately, and this Reddit-like mindset needs to die. HN is a place where we often can actually get devs from companies responding directly and listening to feedback, and this hostility is looked at by all the other devs from those similar companies and remembered when it’ll be their turn.

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)

They said three times "ask me anything" and then didn't respond to a single question. Stop making HN wose by comparing someone dodging accountability to slavery.

Someone made a mistake, owned up to it and fixed it. No one is entitled to more than that for a free software.

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.

> Someone made a mistake, owned up to it and fixed it. No one is entitled to more than that for a free software.

Funny how these "mistakes" only seem to happen in ways that align with the agenda of the supposedly non-evil corporation.

Not sure about the other “mistakes” but this one is way too stupid to be evil :) Hanlon’s razor applies pretty well here.

Pretty sure no one thought “let’s add a lie to every commit and hopefully no one minds. Free Marketing yay!” at Microsoft.

IDK, I heard way stupider and less ethical ideas at work.

Even if I accepted the premise that this is too stupid to be evil, that doesn't change the fact that this would be extremely easy to test for. The fact that they considered it important enough to get this feature implemented without proper testing says plenty about their incentives.

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.

That's a good point, let's see if they come back and respond. It is the middle of the night in the US so they may be sleeping

It is the middle of the night and I am responding. Anything specific you'd like me to respond to?

https://news.ycombinator.com/item?id=47992781

https://news.ycombinator.com/item?id=47992568

https://news.ycombinator.com/item?id=47992475

First comment does not sound constructive - are you interested in my opinion on (n)vim?

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!

It was pretty obvious from your first comment that you were going to get creative with the definition of "constructive".

> 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?

Comments like this are why developers don’t engage directly. The first link is “just asking questions” and implying that the project is rotten. He’s not being “creative” he’s just not engaging in bait.

They’ve done a commendable job responding. Please show some respect when people put themselves in vulnerable situations, otherwise the whole “devs respond on HN” thing will cease to happen.

Perhaps next time you should consult with legal before asserting co-authorship on end users’ code. The appended comment was not “edited with VS code” or “sent from VS code”, it was “co-authored by Copilot”. You do understand that there are legal implications to claims of authorship, right?

To be honest, this question should be directed at the person who made the change/commit:

> cwebster-99 / Courtney Webster / Product Manager at @microsoft working on VS Code and GitHub Copilot!

>> No description provided.

I noticed you only respond to comments that are positive (or neutral). The majority (and the most insightful) comments here are negative, but you seem to ignore them.

their comments are dead, probably related to it being a new account

I really did create a new account to respond :)

Reply on news.ycombinator.com