8 ms·
I'm not sure how leadership or institutional knowledge in the KDE developer community has changed, but since KDE4, KDE developers have gotten very good at non-d
by pxc 5y ago
I'm not sure how leadership or institutional knowledge in the KDE developer community has changed, but since KDE4, KDE developers have gotten very good at non-destructive refinement. The transition from KDE4 to Plasma 5 was much, much smoother than the previous leap. Since then, it feels like efficiency and stability have steadily improved along with feature-completeness.
I guess Qt 6 is out now, and so Qt 5 will soon be unsupported if it isn't already. I wonder how the balance of rewriting and breaking API changes will work out for the Plasma 5 to Plasma 6 transition! Here's hoping the KDE devs figure out how take advantage of the opportunity for helpful/necessary API changes without having to cut or reimplement too many features. What users have got at present is really, really nice
- ognarb 5y agoThe current plans for a port to Qt6 and KF6 are for the moment focused on porting away from deprecated APIs and we are trying to resist the urge to do any bigger changes. Hopefully this will make the transition easy. An overview of all the small tickets is available here: https://phabricator.kde.org/tag/kf6/ https://phabricator.kde.org/tag/kf6/
- pxc 5y agoOver the years, y'all have gotten good at this as a developer community, and this adds to my confidence. :) I'm sure the constraint is frustrating in some ways, but you've built a desktop experience worth conserving as you advance it!