https://bugs.kde.org/show_bug.cgi?id=510753
[email protected] changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #7 from [email protected] --- I want to confirm that Martin Steigerwald is not alone with his situation: A feature which worked well within the specific constraints (working, e.g., around broken Firefox session management) was removed and the reasons to do so are not convincing. "The feature did not work so we removed it" is hard to follow when it worked so well and did no harm. I agree with Martin that now there is no point in keeping activities at all. I have the feeling that the people who decided this did not really use and maybe did not even fully understand the feature. "The end result is one that's inconsistent and unpredictable which is a state worse than not existing so we're dropping this feature." No, this is a reason do document the feature, maybe warn before using the feature and maybe improving the feature. If we drop everything which is not fully consistent and predictable, the world will be empty. "Will I see an impact? […] you can still switch between them as before […]". No, we can't. Cycling between two elements and between > 20 elements is not only a small difference, it's the difference between "keeps the flow" and "unusable". This is also no nice-to-have feature, but an integral part of a power-user's workflow. And there is no alternative, because Plasma was the only desktop with this feature. Everyone depending on activities to get work done now needs to stay with an older Plasma version or needs to compile more or less the whole Plasma themself due to the SONAME changes and the dependencies. What a disservice to the users and what a waste of resources. (and yes, I know that the developers are volunteers and I am thankful for everyone helping out with Plasma, it's just that it looked like if the infamous KDE 4 times were finally over and now the fear of updating starts again) -- You are receiving this mail because: You are watching all bug changes.
