This doesn't shock me in the slightest. It's (apparently) a fairly esoteric bug, and the developer openly wonders whether anybody actually care about it being f

This doesn't shock me in the slightest. It's (apparently) a fairly esoteric bug, and the developer openly wonders whether anybody actually care about it being fixed quickly. For that reason, he asked for a proof in the form of one donation of $1 or more. That's a cheap way to test whether anyone cares about it. In a somewhat related fashion, I have a similar system that I apply to myself on some of my hobby projects. For the more serious ones, I aim to achieve near-100% code coverage in unit tests. One of the side effects is that everytime that I ponder adding a feature not out of need but out of curiosity, challenge or completeness, I ask myself: "do I care enough about it to write tests for it?" It's basically a litmus test for keeping bloat at bay.