That link raises concerns for me that ksyscoca does not. In particular, if I get a random bitflip in my ksyscoca database that renders it unusable, I can recover easily - I just erase the ksyscoca database, and let it rebuild from the configuration files. Similarly, if I end up with a corrupt configuration that I cannot fix through the GUI, I can recover by hand-editing the configuration files, or deleting the bad configuration file, logging out and back in, and reconfiguring that component through the GUI.
With the exception of recovering a corrupt ksyscoca database (which can be detected programmatically and handled without user intervention), these are operations at the level of smart geek, not ordinary user; however, as someone who fixes "computer problems" for ordinary users, being able to say "I've kept most of your personal settings, but you'll need to reset the wallpaper/check your bookmarks/whatever bit was damaged" is a much nicer position than I'm in with Windows systems, where all I can say is "you've lost all your settings."
Copyright © 2018, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds