[TheDong]

Reading through the github issues, the author of this article comes off as very rude and entitled.

I'm on the side of the CoC committee who told the author they engaged without enough consideration or kindness.

Reporting bugs is nice. It's less nice if, when a maintainer asks for a clearer reproduction, you respond with "I already gave you a reproduction, even if you have to edit it a little. I'm not a programmer, all I can give you is some AI spam. I'll leave it up to you to do your jobs" (edited only lightly from what the author really wrote).

[KingOfCoders]

"I'll leave it up to you to do your jobs"

Because the authors expect him to submit a patch when he stated that he is not a developer. That they expect him to reduce the build scripts when he can't do that. Pointing that out, the dev tells him, they don't expect him to be a developer, when some comments above they exactly did that. That is classic passive-aggressive behaviour.

The dev also writes on their page as the top item on what they do:

"fixing paper cuts for users, so all sorts of bugs;"

[jmull]

That's not fair. The ask was this:

"Please try to minimise the steps required to reproduce it rather than producing large scripts with options that definitely won't work for me."

The guy doesn't have to do that, but then, he can hardly expect that people will want to donate their own time to help him with his problem.

Now, I get that he may not have known entirely how to proceed, but instead of asking how, he just says "no" and demands action.

That doesn't leave the dev anywhere to go -- without a way to reproduce the problem they really can't produce a fix.

So only then does the dev say "You're free to propose a patch yourself instead" which I think is pretty obviously rhetorical, meant to point out that there aren't any good alternatives if you don't want the dev's help.

It's all so strangely entitled -- the dev is asking for only the basic minimum of what's needed to actually fix the user's problem and now we've got people trying to shame them on HN.

[TheDong]

Sam didn't expect him to submit a patch at first, he said that _after_ the author refused to cooperate and was an ass.

The expectation to have a reasonable reproducer makes total sense, and if your reporter can't provide a clear reproduction, well, the developer can spend time on the bug but they're not obligated to. Our author was speaking like he was entitled to Sam's time.

I do agree "patches welcome" can be pretty passive aggressive, but in this case it was after our user was already an entitled asshole, and after our user posted AI slop, so I can understand why Sam might feel like being short.

Also, it's just wild that a "non-programmer" is submitting bug reports to a compiler, and then defending themselves with "but I'm not a programmer". Who cares about compiler warnings? Programmers. Compiler warnings are literally just for programmers.

Compilers are one of the projects where the devs actually can and should expect 100% of their users to be programmers, by definition. Why else would you be running a compiler?

I guess maybe the director of the CSI: Cyber show would care about them because they'd make the show look more l33t h4x0r, but I'm really struggling to think of any other audience for compiler errors.

[yeputons]

> Compilers are one of the projects where the devs actually can and should expect 100% of their users to be programmers, by definition. Why else would you be running a compiler?

Following some random instructions for "downloading good GenAI software from GitHub".