Jon said:
The anti-registry cleaner crowd are essentially non-programmers.
True. Instead, we are, for the most part, highly experienced (20+
years, in my case, going on 15 years with registry-based operating
systems) technicians, many of us professionals, who know that all too
many "programmers" are some of the most technically clueless people
extant. All a lot of them do is kludge together (copy & paste) modules
and sub-routines that others have written. I know. I've had to repair
their computers' operating systems often enough. (Yes there are good
programmers out there, but they seem to be in the minority, sadly.)
They do not comprehend the fact that when an application starts up and
reads entries from the registry, that this takes TIME.
/Au contraire/, we realized perfectly well that each application will
have to take a few nanoseconds to read the few pertinent registry
entries. This time, however, is meaningless to humans, and remains
exactly the same whether or not the registry contains extraneous
entries, or whether or not a registry "cleaner" has been used.
They do not comprehend the fact that reading 6000 entries at application
startup will take longer than reading 20.
But we do understand that the registry is an indexed database, and that
no application reads any significant portion of the registry on startup.
Instead, they read exactly those, and only those, entries that they
need.
--
Bruce Chambers
Help us help you:
http://support.microsoft.com/default.aspx/kb/555375
They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety. ~Benjamin Franklin
Many people would rather die than think; in fact, most do. ~Bertrand Russell
The philosopher has never killed any priests, whereas the priest has
killed a great many philosophers.
~ Denis Diderot