Linked by Antonio Ospite on Fri 21st Oct 2011 23:35 UTC
Gnome Antonio Ospite explores Gnome 3 in fall-back mode and tries to make it look and behave more like Gnome 2.32 again. This summer Linus Torvalds made it to the news for complaining about the gnome-shell design; Gnome fall-back mode is the solution for those like Linus who can't - or better, do not want to - use gnome-shell just yet.
Thread beginning with comment 493872
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[4]: Apple Plist, Lazy Loading
by saynte on Sun 23rd Oct 2011 15:14 UTC in reply to "RE[3]: Apple Plist, Lazy Loading"
saynte
Member since:
2007-12-10

Sure, it was a gconf problem, and part of the solution that they design was to make it binary: as far as I know the settings are mmap'd shared and then all processes can read from it at start-up, that's not possible with a text-file.

As far as I know, no-one even used a text editor to modify the settings anyway. There is both a command-line and graphical tool to edit gconf settings, so I'm afraid I don't see the sin in going to binary.

Reply Parent Score: 2

Soulbender Member since:
2005-08-18

as far as I know the settings are mmap'd shared and then all processes can read from it at start-up, that's not possible with a text-file.


What makes you think it's not possible to mmap text files? it works just as well with "binary" as "text" files.

Reply Parent Score: 3

saynte Member since:
2007-12-10

Because you still have to lex and parse the text file, which is a lot more complicated than the system needed to examine GVariant data. The dconf system was basically built to be very fast, faster than text, and I really can't see the disadvantages in designing it for speed.

If you don't like their decision to use dconf: that's fine. But please, don't insinuate that they are somehow amateurs for not using text-files. The dconf system wasn't a premature optimization, it was in response to a performance problem.

Reply Parent Score: 2