https://bugs.kde.org/show_bug.cgi?id=354802
--- Comment #135 from Nate Graham <n...@kde.org> --- Nick, evidently this bug is priority #1 for you. But unfortunately for you, clearly is it not as high a priority for the developers, because we are fixing other things rather than this. It is telling that you see all of that other work as "insignificant." I understand that it seems that way to you because this specific issue is your top priority. But for people who are not you, other issues are their top priority. Understand that if somebody spent a few days fixing this, they would be neglecting other issues, and people in those other issues would be saying the same things there. "Developers don't care!" "How can this bug still exist after X years!?" etc. The very difficult job of a developer is to figure out whose top priority to prioritize, because there are always more bugs than there are hours in the day to fix them. That time is previous, and discussions like this consume it and make people feel exhausted. I have now spent over an hour reading and writing text in this bug report today. Not fixing the bug. Not investigating it or scoping out work. Just participating in this discussion. That's time I haven't been spending on actually getting anything done. But of course, when developers stay out of discussions like this because they *do* prefer to get things done, people complain that developers are ignoring bug reports and disrespecting users. Have a little empathy. This is a hard job. If you want to help this bug get fixed. I provided a list of 5 potentially effective actions. Complaining about it in the bug report or posting "this is still a problem" after every release is not one of those effective actions. :) -- You are receiving this mail because: You are watching all bug changes.
