Thanks for the shout out re KNetworkManager. I'd qualify the 'interface struggles' observation quoted from the KNetworkManager dot article by saying these actually took place in the 11.1 release cycle. For 11.2 we had a direction and it was pretty much plain sailing.
Fonts are one of those things it seems hard to 'get right out of the box' on everyone's screen. Every time we tweak font hinting settings on a release, a different section of the userbase screams because fonts just went ugly on their default install, and subjectively one person's 'clean' is 'spidery' to another, who prefers 'smudgy'. What kind of 'atrocious' was it for you? FWIW the default fonts look great to me on a ThinkPad X60, a HP Mini 2140 and a HP LP2065, and the customised fonts that you used on the screenshots look fine to me, if a bit clumpy on the Konqueror/Kontact menu and toolbars.
The Akregator crashes are likely bko#116482 or bko#133407. The Akregator developers acknowledge there are design problems in the way feeds are stored and have said they aren't in a hurry to fix them, because this code will be removed when Akregator is ported to Akonadi (for KDE 4.5). Redesigning apps' backends for them is kinda out of distributions' remit, so I guess you'll see this anywhere. As damage limitation, I might disable the Kontact integration.
But which KDE settings refused to apply? I can't believe that the KDE app settings infrastructure is generally broken, so if a few apps are advertising settings that they don't save, we want to know about it and fix them.
Copyright © 2018, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds