We're all glad to see that registry fixed those performance issues.
Well, that was the theory anyway.:)
Too bad that only works that way in theory. The registry rarely gets used properly, and almost every app leaves tons of crap behind after an install...
I just said it allows developers to store everything in one place. I never said that developers always use it properly.:)
Actually, the registry was created to alleviate the issue that was seen in Windows 3.1 and below --.INI files everywhere on the hard drive. Application developers would sometimes put their INI files in the \windows directory. Sometimes they'd put them in the application folder. It made things difficult from a backup perspective. There were also performance implications.
The registry allows developers (and the OS itself) to store all the configuration information in one database that can then be backed up regularly (the OS does this itself, but you can also manually back it up).
Slashdot Mirror
We're all glad to see that registry fixed those performance issues.
Well, that was the theory anyway. :)
Too bad that only works that way in theory. The registry rarely gets used properly, and almost every app leaves tons of crap behind after an install ...
I just said it allows developers to store everything in one place. I never said that developers always use it properly. :)
Actually, the registry was created to alleviate the issue that was seen in Windows 3.1 and below -- .INI files everywhere on the hard drive. Application developers would sometimes put their INI files in the \windows directory. Sometimes they'd put them in the application folder. It made things difficult from a backup perspective. There were also performance implications.
The registry allows developers (and the OS itself) to store all the configuration information in one database that can then be backed up regularly (the OS does this itself, but you can also manually back it up).