|
|
|
|
|
by nchmy
10 days ago
|
|
Sorry for the ninja edits. Writing from phone and didn't think there'd be people replying right away. Seems like we're in agreement. But I reiterate that it's not a good rule if it should be regularly broken, for the good. Thus, for a project that's been around for seemingly a very long time, it's hard to imagine that they haven't had ample time and feedback to vastly improve the wording of it all. Thus, they seem to be content that it expresses exactly what they want it to. |
|
I do think you're simply reading their rule in a way that's not intended by them. Could the rule be written to convey the intent more clearly? Yes, I think so. Is it only their own responsibility how the rule is interpreted? No, I don't think so.
The hacker news guidelines ask us to:
> respond to the strongest plausible interpretation of what someone says, not a weaker one that's easier to criticize. Assume good faith.
This is good advice in general. It is your choice to pick an the interpretation that you disagree with the strongest, and subsequently use it to condemn them: "puts me off entirely", "no room for nuance", and (paraphrasing:) it's on them to prevent me from interpreting the rule in the most severe way.
No. The spirit of the rule is clear. The nuance is there. What you do with it, that is all you.