Comment by selcuka
> If something isn't completely breaking the use case of a program, or doesn't have any viable work around, I just don't expect it to ever get fixed
Yep. That has always been the general industry sentiment [1]:
> Here’s another bug that’s not worth fixing: if you have a bug that totally crashes your program when you open gigantic files, but it only happens to your single user who has OS/2 and who, for all you know, doesn’t even use large files. Well, don’t fix it. Worse things have happened at sea. Similarly I’ve generally given up caring about people with 16 color screens or people running off-the-shelf Windows 95 with no upgrades in 7 years. People like that don’t spend much money on packaged software products.
[1] https://www.joelonsoftware.com/2001/07/31/hard-assed-bug-fix...
You missed the important part:
>But mostly, it’s worth fixing bugs. Even if they are “harmless” bugs, they may reduce the reputation of your company and your product, which, in the long run, will have a significant impact on your earnings. It’s hard to overcome the reputation of having a buggy product.