gconf typically uses an XML backend, while
dconf uses its own binary blob. From that change alone you can draw up some points:
- Binary read access is far faster than parsing XML
- According to dconf's design section, a Gnome login consists of thousands of read operations and only a few writes. To
gconf that's thousands of stats, thousands of reads and thousands of parsings.
dconf's binary blob would blitz through those without bogging the system down with umpteen thousand IOPs.
- XML is more portable
- XML is largely human -readable and -editable.
- A file-based system can be separated and portioned without much hassle
- Corruption of a monolith binary file could mean the whole thing dies. Single file corruption only hurts that segment in
A lot of the arguments are those levelled for and against the Windows registry.
As I understand it, the interface onto this settings back-end would be the same as
GSettings. This would allow distributions and users to chose one and switch out if they needed to.