I think that KDE's track record shows that devs do not remove stuff just because. Quite the contrary.
But sometimes stuff does get removed and often it is because or it is unmaintained (and been so for a while), or because it is built on some old technology that cannot be replicated in the new environment without a complete rewrite.
In both cases, the reason a feature is discontinued boils down to a lack of resources.
Fortunately, the solution is simple: do your part.
KDE is a porous, grassroots and welcoming community. Join us and become part of the effort to build one of the largest and most diverse collections of end user, publicly-owned, free software projects in existence.
I know, I know: "but I can't code", etc., etc. But there are many things you can do to help. You can help organise Akademy 2024, you can translate menus and system messages, you can write documentation, draw wallpapers, design icons, edit videos, support booth staff at events, triage and report bugs, or just donate and contribute to financially supporting devs who still have to hold down pesky day jobs that get in the way of coding for KDE... The list goes on and on.
The point is, regardless of your level of technical knowledge, the more resources you free up elsewhere, the more time the people who do know how to code will have to maintain and translate software and features in the new Plasma 6 environment.
I've recently switched from Gnome to KDE in preperation for Plasma 6. I'm definitely noticing some rough edges even on 5.27, so I'm highly looking forward to 6.00
That's how I felt with KDE 1 and 2. I left it alone for a while and recently came back to KDE 5 after getting a steam deck and now I've switched my desktop to it.
@kde@[email protected] In a sense it feels long overdue, but it also does take time and feels very new...
My question is what happens to Qt5? I feel like it's because of #KDE it continues to be maintained at all, and yet many other projects still utterly depend on Qt5, even believe they don't need to migrate to Qt6 or otherwise refuse to. I believe HelloSystems is in this category.
I wouldn't expect so. Firstly, the deadline for packages getting into a distro is usually several months before the release date, and secondly that they'll likely (understandably) cautious about an x.0 release for production.
@[email protected]@[email protected] excited! Always loved KDE, but finally made the switch to an AMD GPU this month and finally getting to enjoy kde with Wayland and it so good!(once I disabled freesync on my monitors so my computer would stop crashing)
@kde@[email protected] what I do like from what I have seen of this is the idea, which I love in Xfce, of trying to produce the best possible version of KDE at the time, rather than wasting real user's time by completely re-imagining and re-inventing what a desktop even means to stroke private egos. That is the difference between greater value construction over time, and it's continual destruction.
@[email protected]@[email protected] wake me up when you restore the ability to place multiple application tabs in a single window. Many have been up in arms about the inability to use different backgrounds on different desktops for years. But the loss of the ability to combine applications in tabbed windows is a more serious regression in my opinion.
This is our standard answer to people who need reminding that KDE is a community powered by volunteers and that each contributor works for free to bring you the best software they can make with the means they have.