Linked by Thom Holwerda on Fri 22nd Jan 2010 17:06 UTC
Permalink for comment 405556
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 22:06 UTC
Linked by Thom Holwerda on 05/21/13 21:45 UTC
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
More News »
Sponsored Links



Member since:
2008-07-15
You make it sound like the registry is magically free from file latency. Guess what, underneath it all the registry is composed of files as well. It might be faster as far as an API goes, but these days you can do the same thing just as quickly with XML. Gconf on Linux, as well as OS X Plists, are XML files and both have APIs that are simple like that of the registry. At this point, the registry has become a complicated rat's nest and is being used for too many things. I hate trying to remove some unwanted ad-ware and having to go into a registry path such as:
HKEY Classes Root\CLSID\0xa2d9ff48\001a4dd3... etc etc. Ridiculous, and pointless to boot. It wouldn't be so bad if legitimate programs used the registry in a sane fashion, but they don't. At least with OS X Plists and Gconf the legitimate keys and folders have sane names, anything odd sticks out immediately.