Hacker News new | ask | show | jobs
by devenblake 1866 days ago
It wouldn't have been that hard to just ask "why?" rather than marking it as something that needs fixing.
2 comments

You are misunderstanding (or perhaps misrepresenting) the situation.

Quote from the person who filed the issue:

> I don't understand why you think my behavior is entitled. I genuinely thought it was a bug because the colors didn't look right to me, in the sense that some of them don't match what is expected from their name. I still think that because the colors are distant from their expected neutral form this makes it a poor default theme.

https://github.com/alacritty/alacritty/issues/1561#issuecomm...

The original bug report was perfectly respectful, and this is a perfectly respectful reply to the revelation that it's "not-a-bug".

The maintainer is being aggressive and looking for a fight, venting their frustrations on some person who is trying to be helpful. All they had to say was, "Sorry, this is the default color scheme, we prefer it this way and I'm not concerned that the color isn't exactly green to everyone's eyes. Thanks for your interest!" and close the issue.

> The original bug report was perfectly respectful

Describing someone else’s work and choices as ‘poor’, especially when you didn’t pay them anything for it, is disrespectful.

Not saying this is the case, but the reporter could very well be a non native speaker. As a non native myself, I don't see anything disrespectful in their report.
You mean from the guy who opened the issue? It started with a simple “the colors don’t seem to be right” in search of comments. Reporters cannot tag issues as bugs.
Alacritty has an IRC channel for discussions, and their contributing guidelines make it clear the issue tracker is for bugs and feature requests. I can see being frustrated with someone raising this issue as a bug.
The reporter thought it was a bug. CONTRIBUTING.md didn't exist at the time. And it doesn't say that.
It says to use the issue tracker for bug reports and feature requests. Was there nothing in the README at that time saying anything similar?

Regardless, people thinking whatever thing happened to aggravate them about a project is “a bug” is a huge and constant drain on open source maintainers. In this case, as other people have pointed out, there were other threads already where default colors were discussed that this person could have found, and even passing familiarity with terminal color schemes would show that much of the time, what the escape codes define as “green” or whatever is a very different color. That’s why the color schemes exist, so that you can redefine what “green” is for your own tastes. I can’t imagine opening an issue suggesting that a project change their default color scheme not because it’s inaccessible or illegible, but just because I don’t like it or it doesn’t look like some other project.

It says the right place for bug reports and feature requests is the issue tracker. It doesn't say nothing else belongs there. Actually it says the issue tracker is the right place for any other questions about contributing too. And it just says IRC is more immediate and direct.

README.md said "If you run into a problem with Alacritty, please file an issue." at the time.[1]

I don't see where anyone pointed out what you said multiple people pointed out. The closest I see is 1 person said there are 88 color related issues now. Feel free to point out a specific issue you think the reporter should have found.

It isn't clear they expected the colors to match exactly. The default green looked yellow to them. And changing the default colors would be a valid feature request if nothing else.

[1] https://github.com/alacritty/alacritty/blob/9bc888fbe581efeb...

It’s not a valid feature request when the colors are already all configurable, so anyone can change them to be however they like. The green being a little yellower than this person preferred is not a problem worthy of bothering the people who wrote the software. Non-issues like this sap the will to live of people building cool things for free on their own time.

Edit: personally I don’t have the time to go digging through old repo issues of a project I don’t even work on for the sake of arguing about one entitled user. I do maintain several projects, and I definitely feel that these kind of aggressive non-issues are the worst.