> I would have told people to pound sand, personally, given the absolute vitriol sent his way.
Sounds like a great way to get even more vitriol, and continue to get it for years afterward. Every time you released a new version, there it’d resurface again. Sure, you could block some people on GitLab, but then you’d see it on social media or what have you.
Or you could just move it out to a plugin quickly (which is what happened, the beta for this version was out in a couple of days) and curtail the backlash.
Being angry at the people angry about you is not a practical solution if your goal is piece of mind.
Which is all fine and dandy as long as you never have to interact with those people, but in this case the author would absolutely have to do that. If not directly in their issue tracker (though certainly there), then in every conversation about their project from then on. That would be quite tiring for most people and lead to burnout.
> Being angry at the people angry about you is not a practical solution
If you don’t think so, I’d be interested in understanding what you see as the principal difference between those statements. To clarify, I was also referring to (internet) strangers.
In sum, why even bother in this case? Just rip it out to a plugin and never think about it again. Now that is pragmatic.
Sounds like a great way to get even more vitriol, and continue to get it for years afterward. Every time you released a new version, there it’d resurface again. Sure, you could block some people on GitLab, but then you’d see it on social media or what have you.
Or you could just move it out to a plugin quickly (which is what happened, the beta for this version was out in a couple of days) and curtail the backlash.
Being angry at the people angry about you is not a practical solution if your goal is piece of mind.