That's great. But even if you don't, the beauty is that the code is out there now.
> Only if you have found the two or three solutions that the community likes most and you are still unsatisfied, only then start coding.
Nah. I mean, sure, if it was for an actual business decision or for something that directly affects productivity workflow, due diligence is warranted.
But I'm never going to tell someone that they shouldn't have made something. Tell them there's something better, yes. Tell them that a different project does it in a more intuitive or robust way, certainly.
This nose-thumbing trend of not just ignoring code you don't like, but actively discouraging the release of code you might not approve of?
Yeah, no.