Linked by Thom Holwerda on Thu 19th May 2011 18:59 UTC, submitted by fran
Permalink for comment 473974
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/21/13 15:53 UTC
Linked by Thom Holwerda on 05/20/13 22:43 UTC
Linked by Thom Holwerda on 05/20/13 21:50 UTC
Linked by Thom Holwerda on 05/19/13 23:15 UTC
Linked by Thom Holwerda on 05/19/13 23:11 UTC, submitted by Drumhellar
Linked by Thom Holwerda on 05/18/13 21:06 UTC
Linked by Thom Holwerda on 05/18/13 7:37 UTC
Linked by fran on 05/18/13 1:38 UTC
Linked by Thom Holwerda on 05/17/13 23:35 UTC, submitted by kragil
Linked by MOS6510 on 05/17/13 22:22 UTC
More News »
Sponsored Links



Member since:
2005-07-07
now, go and read proposal again.
systemd proposed unified interfaces to solve duplication, which doesn't impose new problem, but rather solves one. major reason why gconf came to be is simplification for developer.
another thing you failed to grasp is yours so called text configurations. they would be great ... if there would be one standard to read/write them. look httpd.conf, smb.conf and inittab. hell, there is no standard how you read/write them. enter xml and you get configurations unified. gconf is nothing but text files formated by xml spec.
try looking at s-c-t from ximian and read why it never saw the light.
personally, my biggest wish is that every project would adopt xml and also provide converter from old config standard to xml or back. everyone would be happy, those editing manually and coders who write gui tools.