Return to Answer

This needs to go away. Now.

The rule is actively harmful to this site. Its theoretical benefit is offset thousandfold by the harm it does.

See Larian’s lament. Fortunately, the answer in question has since been merged but the harm has been done:

You didn't want to hear the names my wife called Stack Exchange after she put so much into her answer. I had to rescue it as she just walked away. Not sure if she will come back...

(Emphasis mine.) I can’t blame her. Talk about a bad UX. I have zero tolerance for that on other badly designed sites, we shouldn’t have that on “our” site.

And to make it worse, we don’t even know how many answers we’ve already lost due to this. But we do know that the quality of some answers has suffered due to the rule.

This needs to go away. Now.

The rule is actively harmful to this site. Its theoretical benefit is offset thousandfold by the harm it does.

See Larian’s lament. Fortunately, the answer in question has since been merged but the harm has been done:

You didn't want to hear the names my wife called Stack Exchange after she put so much into her answer. I had to rescue it as she just walked away. Not sure if she will come back...

(Emphasis mine.) I can’t blame her. Talk about a bad UX. I have zero tolerance for that on other badly designed sites, we shouldn’t have that on “our” site.

And to make it worse, we don’t even know how many answers we’ve already lost due to this. But we do know that the quality of some answers has suffered due to the rule.

This needs to go away. Now.

The rule is actively harmful to this site. Its theoretical benefit is offset thousandfold by the harm it does.

See Larian’s lament. Fortunately, the answer in question has since been merged but the harm has been done:

You didn't want to hear the names my wife called Stack Exchange after she put so much into her answer. I had to rescue it as she just walked away. Not sure if she will come back...

(Emphasis mine.) I can’t blame her. Talk about a bad UX. I have zero tolerance for that on other badly designed sites, we shouldn’t have that on “our” site.

And to make it worse, we don’t even know how many answers we’ve already lost due to this. But we do know that the quality of some answers has suffered due to the rule.

This needs to go away. Now.

The rule is actively harmful to this site. Its theoretical benefit is offset thousandfold by the harm it does.

See Larian’s lament. Fortunately, the answer in question has since been merged but the harm has been done:

You didn't want to hear the names my wife called Stack Exchange after she put so much into her answer. I had to rescue it as she just walked away. Not sure if she will come back...

(Emphasis mine.) I can’t blame her. Talk about a bad UX. I have zero tolerance for that on other badly designed sites, we shouldn’t have that on “our” site.

And to make it worse, we don’t even know how many answers we’ve already lost due to this. But we do know that the quality of some answers has suffered due to the rule.