5 ms·
Your entitled behavior has no place in this project or its issue tracker
- djohnston 6y agoI've seen a lot worse on github, it doesn't seem like that big of a deal, the filer didn't have a bad attitude IMO, but maybe I lack context.
- deleted 6y ago[deleted]
- donkarma 6y agoI gotta agree, if the application wants green it should get green, not yellow
- Justin_K 6y agoBut the color is mostly green
- donkarma 6y ago#B9CA4A definitely leans towards yellow in my opinion. At best, it's a mix of both, which is terrible still
- DonHopkins 6y agoWHAT IS YOUR DISPLAY? display = XOpenDisplay("unix:0"); WHAT IS YOUR COLORMAP? cmap = DefaultColormap(display, DefaultScreen(display)); AND WHAT IS YOUR FAVORITE COLOR? favorite_color = 0; /* Black. */ /* Whoops! No, I mean: */ favorite_color = BlackPixel(display, DefaultScreen(display)); /* AAAYYYYEEEEE!! */ (client dumps core & falls into the chasm) https://donhopkins.medium.com/the-x-windows-disaster-128d398ebd47 https://donhopkins.medium.com/the-x-windows-disaster-128d398...
- deleted 6y ago[deleted]
- devenblake 6y agoIt wouldn't have been that hard to just ask "why?" rather than marking it as something that needs fixing.
- nerdponx 6y agoYou 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#issuecomment-422874825 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.
- chrisseaton 6y ago> 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.
- thiht 6y agoNot 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.
- jiofih 6y agoYou 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.
- anothernewdude 6y agoI don't think we derive much benefit from attempting to create or highlight drama
- nerdponx 6y agoI don't think this is "drama" unless people make it into "drama". Maintainers have a difficult job. The open source world is still young and its social norms are evolving. A sober ongoing discussion thereof is very warranted and seems quite on-topic for Hacker News.
- jiofih 6y agoThat was.. unexpected. Seems like every project maintainer is on edge these days.
- splintercell 6y agoThis is from 2018 btw.
- oneplane 6y agoThere aren't a lot of options out there when you are a maintainer. You either stamp out anything that you know you are probably not going to be able to sink time and energy in to (either by ignoring it and letting the issue/project die a silent death or by commenting a $WONTFIX message) or you burn out.
- nerdponx 6y ago"WONTFIX, sorry" would have been more respectful, much faster, and much simpler than this.
- dopamean 6y agoRegardless of the whether or not the filer is correct the maintainer did not need to respond the way he did. It was unnecessarily hostile imo.
- DonHopkins 6y agoArguing about colors is literally bikeshedding. https://bikeshed.com/ https://bikeshed.com/ http://phk.freebsd.dk/sagas/bikeshed/ http://phk.freebsd.dk/sagas/bikeshed/
- nerdponx 6y agoEverything is bikeshedding until it isn't. What if there's a product requirement to paint the shed red? That's literally what happened here, something didn't look green when the user expected it to be green, and the user thought it was a bug.
- falcolas 6y ago> What if there's a product requirement to paint the shed red? Then you argue over the paint brand, how much to buy at what price, rollers vs sprayers vs brushes, and so on.
- throwaway3neu94 6y agoActually, often you do pull out your Pantone or HKS color matching cards to work out which specific red is required, whereas you don't care which brand etc. your print service uses. (src: merchandise printing) (Also, at one place I worked we bought some used server racks that we were told had been painted in a very specific company standard server rack beige by the previous owner megacorp.)
- Bancakes 6y agoHow is it bikeshedding when somebody inexplicably makes arbitrary changes to popular software and UX?
- Shadonototro 6y agoit is UX issue no wonder linux has shitty UX
- snthd 6y ago(2018)
- uglygoblin 6y agoThe title should be updated with the fact that this is from 2018.
- temp8964 6y agoTotally unnecessary comment targeting other people's "behavior". Just say it's part of default coloring theme and you are welcome to create your own. Isn't this enough?
- chrisseaton 6y agoDon't you think 'Aparently the defaults are poor' was an extremely aggressive way to put the point across? Calling someone's work 'poor' is nasty.
- ramphastidae 6y agoI don’t see entitled behavior ... but I do see someone on the verge of burnout, making feedback about the software about themselves, and lashing out. I wouldn’t want to work with such a person.
- Bostonian 6y agoI often see GitHub projects, maybe from people who are not native English speakers, with bad grammar in the Readme.md . Is it OK to create an issue pointing out spelling and grammar errors and suggesting fixes? Resolving such an issue will not improve the code but can make the project more accessible.
- vbezhenar 6y agoMy English is poor and I'd love such fixes. But, I guess, it comes down to a person. What I think is worth discussing before suggesting are "polite correct" fixes like "blacklist -> blocklist", "master -> main", "he -> them", etc. Not everyone is fine with this new agenda and one might find those fixes offensive. I'm not saying that those fixes are not appropriate everywhere, just that it's worth discussing before submitting to avoid a pointless debate.
- mplanchard 6y agoPersonally I would much prefer this, especially as a PR, than nitpicking about default (and configurable) colors like in the linked issue. Even as a native English speaker, I frequently make typos, and I’ll often wind up with weird phrasing or grammar due to consecutive rounds of editing things out.
- FlagBrigade 6y agoAnother post flagged. Is anyone else getting sick of the abuse of the flagging system?
- eugeniub 6y agoAre we supposed to comment on a discussion from 3 years ago?
- rognjen 6y agoInterestingly enough there seem to be 88 issues related to colors https://github.com/alacritty/alacritty/issues?q=is%3Aissue+in%3Atitle+color+ https://github.com/alacritty/alacritty/issues?q=is%3Aissue+i...
- mplanchard 6y agoA lot of people are saying the maintainer’s reaction was over the top. I don’t think so, but I think it comes down to your perception of Issues, specifically whether you view them as an area for bug reports vs an area for discussions. Alacritty is a really popular project. It probably gets a ton of issues being opened. As a maintainer, every single issue is time you’ve got to take out from stuff you’d rather be doing. From that perspective, someone popping in to complain about the default colorscheme because it doesn’t look like their previous editor, when they can easily change the colors to be however they like, is going to be super frustrating. This is doubly true if you don’t usually view issues as a spot for general discussion. I can see that the person who posted the issue was trying to help, but honestly it’s just not very helpful. A lot of people view airing their own personal dissatisfaction with a tool as being helpful, and generally that’s not true. Edit: also just noting that alacritty has an IRC channel linked on their README for discussion of things that aren’t bugs.
- yoav 6y agoBoth sides of the github issue discussion are incredibly fragile, defensive, and sensitive. The conversation should have been: A: “Hey this green is legit yellow, this is very confusing for new users. I’m not sure if this is a bug because it’s so abnormal I’ve never seen this anywhere ever before” B: “Ya we did that on purpose, because we hate green, please use the IRC channel in the future to determine if something is a bug or something we did because of our dislike for the color green first in the future. Our github time is more important than our IRC time. Anyone who doesn’t know all our rules will be attacked and banned from the community. And here are some other themes for people that like green to look green instead of yellow, please enjoy.” A: “oh cool, thanks”
- fortran77 6y agoActually, nobody should ever be made to feel bad for reporting a bug. Thank them, explain why you're closing it, offer an alternative, and close it!
- loopz 6y ago1. This isn't worthy of HN. 2. The default colors are all wrong (my own unwavering opinion). If the maintainer wants his own defaults colors, he can apply his own configuration for this and offer such scheme to those who prefer the same choice. 3. We all can crack at some point in time. So we need to be big and allow the space for both such discussions and the occasional blowout, but at the same time not be abused by it. Arrogance only reflect really badly on yourself in the end, but it can happen to the best of us. 4. Maybe someone is color-blind? Who knows? We must expect variety.
- deleted 6y ago[deleted]
- mcint 6y ago1. agreed. Hard to reply in ways that don't partake in and invite further polarizing discussion. 2. Agreed. Expressing it in HSL colorspace makes it pretty clear how close to yellow, and far from the large space of expressible greens. In RGB, yellow is the region near R% = G%, so #b9ca49 is, at a glace, still close to yellow. https://www.w3schools.com/colors/colors_picker.asp?colorhex=b9ca49#huecontainer https://www.w3schools.com/colors/colors_picker.asp?colorhex=.... (4) Accessibility was mentioned and deuteranopia, red-green color blindness, is most common. Perhaps this shade is distinguishable. Accessible defaults are worthwhile.