A "registry" isn't, in and of itself, a bad thing
It's essentially a database of config options
and you can get some pretty big speed improvements from a database as opposed to parsing individual flat files
If something has in inherent hierarchy and structure, then you can optimise the speed of random accesses by bunging the whole lot into a tree structure
Gnome does this with it's gconf
Where Gnome wins out, is that it's database is XML based
Windows uses Jet for it's registry (the same abysmal DB engine that powers MS Access.....)
But more importantly, Gconf only deals with gnome stuff (app agnostic)
The Windows registry tries to deal with everything
This type of organisation is brilliant for static structures
(the tree stays the same, it's just the values that change)
but a poor design for non-static structures, where the tree is changing
When a Windows app is installed, it changes the tree structure (adds it's own branches
When the app is uninstalled, it deletes the values but leaves the empty branches behind
Having lots of empty branches just slows down searches
The ideal solution is to have static structures in a tree, and dynamic stuff in flat files
(maybe showing my bias here, but this is exactly what Gnome does)
A central database (registry) of stuff is great for certain things
crap for others
Windows bungs everything in a database, and over time it clogs up with cruft
|
|
Bookmarks