https://bugs.kde.org/show_bug.cgi?id=340982
--- Comment #237 from brenb...@brenbarn.net --- (In reply to Nate Graham from comment #235) > If this were clear-cut, it would have been done ages ago. Instead we have a > trade-off to make: > 1. Add the feature for only KDE apps, and then your non-KDE apps will > display all their formats incorrectly, or at least inconsistently > 2. Stick to the status quo of consistent systemwide formats, but without > this desirable feature > 3. Attempt to work upstream to change the whole world so that we can have > all of the upsides with none of the downsides > > You're not wrong that #3 is unlikely, which effectively makes it a #2. > > I understand that you personally might prefer #1. However at the moment > KDE's developers do in fact want to have KDE's apps play nicely with the > world around them. This is far from something we ignore and is in fact a big > deal to us. It's why we have a nice-looking GTK theme, a GTK settings > synchronization service, a first-class implementation of the portal system > for sandboxed apps. It's why we work upstream on wayland protocol work > rather than just using private protocols and calling it a day and why we > just implemented support in Plasma 6 for the FreeDesktop standard sound > theme spec. > > You might personally prefer that we had different priorities, and that's > fine. We can't make everyone happy. But we can explain our reasoning and > hope that people can accept that sometimes there is no ideal solution and we > have to pick from among a menu of imperfect options. I don't really understand this logic. You're saying for users who want things to look a certain way, it's better for them to have everything look bad than to have some look bad and some look good? KDE can never fix every problem, but what's the use in not fixing something just because doing so would make the unfixed non-KDE stuff look "inconsistent"? -- You are receiving this mail because: You are watching all bug changes.
