If somebody thinks "this product is flawed in this specific way" is being mean to them, that person might not be well-suited as a programmer.

If somebody thinks "this product is flawed in this specific way" is a bug report and an indicator of something to be fixed (assuming the bug report is valid, some bug reports aren't), then that person has the hacker ethos and will produce good products.

There are a couple comments that do fit the "being mean" framing, yes. But most of the comments here are along the lines of "here's a flaw in the product which would make it better if it was fixed". For example, my own comment pointing out the unreadability of the LLM-generated README: I pointed out a flaw and how to fix it. (I also made a point of mentioning that it seemed like a useful tool. I didn't spend too long on that point, because the bug report ("make your README human-readable, please") was the main point of my comment). But if someone were to take a comment like mine, pointing out a flaw and suggesting a way to fix it, as "being mean", then I would kindly suggest that that person find a different job than software engineering. Because every time the compiler says "Syntax Error", it's pointing out a flaw in your code. Any person who can't handle flaws in their work being pointed out, can't handle this job.