https://bugs.kde.org/show_bug.cgi?id=434877
--- Comment #50 from bugs.7n...@aleeas.com --- (In reply to Nate Graham from comment #44) > We know this is an issue; that's > why it's open and in the CONFIRMED state. Further criticisms don't help > anything. if you want to help, try to fix it. Thanks for acknowledging the issues. I think by making the new system monitor the default while it still has such tremendous regressions compared to the old one, it's easy to think that the gravity the change had on some users was not anticipated. > Nobody wants to spend their (often free!) time reading [...] their product > being insulted. I love the optics of the new system monitor. Do you personally consider the new one a suitable replacement of the old one in the near future, though? I can get behind the "the old one wasn't maintained" reasoning, and I'm really happy y'all have already resolved many of the ~10 bug reports I raised about the new one (as constructively as I could). Meanwhile since you're asking for empathy towards maintainers, is it difficult to conversely see that users would be unhappy to see such massive usability downgrades in everyday tooling? Wouldn't it save a lot of energy for all of us if we let these things bake a little bit further instead of over-eagerly changing defaults? I've had the same sentiment for the QML rewrite of the KCM modules, where the end result turned out to be a great improvement in the long run but the initial roll-outs had been very bumpy. > Anyhow, the offer stands. If a return of KSysGuard is acceptable then I'm > willing to put in the time and effort to get that done. It is not a long term solution, I know that. It's an intermediary fix till plasma-systemmonitor is in good shape again. I'd also really appreciate if this proposal could be nodded off. I do want to see the new applet return one day, or perhaps shipped side-by-side (as I think it already was at least on my distribution). -- You are receiving this mail because: You are watching all bug changes.
