Originally posted by: Chadder007
Microsoft should have never created the Registry in Windows.
It's funny how often people fault Microsoft for decisions they have made over time, in response to historical conditions that no longer exist. Windows has been around 17 or 18 years now, DOS even longer. Back in the late eighties and early nineties most programs stored their configuration locally, in .ini files, or proprietary formats. MS thought a more centralized standard repository was a good idea, as did most customers, so they put it in. It worked pretty well for years. But people now install so much stuff, the stuff they install is so much more complicated, and the people who script install packages (or more accurately, uninstall packages) suck at it so badly, that the registry has become a vulnerability rather than a benefit. They are now pushing application configuration back toward the file system using the user directory structure and XML data formats, and supporting this model through APIs in the .Net framework. Things change.
Registry "bloat" and system performance... I don't buy that there's much of a link at all, except in specific circumstances. Those are pretty much limited to when a program tries to read bad registry data and either hangs or slows way down. Other than that the effects would be that the registry would be larger on disk, take more time to search, etc.
But unless your registry is like 50% old, stale keys, I can't see this really making a difference.