https://bugs.kde.org/show_bug.cgi?id=354802
--- Comment #140 from Nick Stefanov <m...@abv.bg> --- (In reply to Nate Graham from comment #135) > 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. :) Don't get me wrong, Nate. I don't depreciate dev's work. On the contrary - all of you make wonderful work and that's why KDE is the greatest DE ever. But please understand - this bug isn't priority #1 just for me. If a bug exists only in one DE, it's a real problem. If a bug is on the face of that DE, that's a realy big problem. Think about it - even Windows 95 works better in this regard. Every DE have a desktop and everywhere it's used with one single purpose. We can't use our desktops and that's a big problem. That's it.(In reply to vindicator from comment #138) > I was going to say the same thing, but also add that it's already been said > that they can't replicate the issue on their side. > > That makes fixing the issue much harder. And if you have other bugs reported > to you that you can replicate or have a backtrace that makes finding the > cause easier, it's a no-brainer to attack those bugs first rather than poke > around in other code to try to blindly figure out why a desktop quirk is > happening (with no idea how long it'll take to find it) and leaving those > easier bugs untouched. What about this 100% reproducible bug? https://bugs.kde.org/show_bug.cgi?id=360478 Nobody look or work on it. And the bug may be relatively new but actually the problem is here for years, even in KDE 4. Nothing, zero effort, zero interest from devs. It's a very good occupation for users to rearrange their icons X times a day. I also like it. What I'm sayng? I adore it. -- You are receiving this mail because: You are watching all bug changes.
