Comment by cxr
3 years ago
This comment-and-response pair has a really weird "shape".
You're offering a retort to someone who is communicating their position that you ought not do something, where the retort consists of nothing more than explaining that people are doing it. Yes, clearly. But what the person you're responding to is arguing is that you ought not do it.
Consider the following hypothetical:
Person A: Here's little advice: don't take up smoking. Smoking is bad for you.
Person B: Yet people smoke—my cousin, for example.
The point of the other comment wasn't that it isn't happening or that it's physically impossible to even try. Indeed, the fact that it's being done—or that people are attracted, at least, to trying to do it—was rather the entire premise of their "word of caution".
I see a different "shape". To me it looks like the same accessibility song and dance that happens every time a GUI library is the topic.
Is accessibility not a worthwhile concern?
I wouldn't go that far. But "this lacks accessibility" isn't sufficient reason to rule something out, imo. It's better for a piece of software to exist, without accessibility accommodations, than it is for it to not exist at all.
4 replies →
What answer are you expecting? This question is borderline flame bait.
3 replies →
This is for the creators to decide. Nobody else has a say, really.
2 replies →
Probably not for internal custom tools.
5 replies →
If the topic is a tool that's missing an important feature, then of course people will discuss why that tradeoff has been made.
Ship or don't. If the calculus boils down to this, then making suboptimal choices isn't necessary wrong.