But it’s a perfectly functional and sensible solution for storing system configurations.
No. It was not. The concept was OK, but the execution was not. Even Microsoft didn’t know what was in there. The design was horrific. They could have used keywords, they could have had a data dictionary, they could have standardized it. They could have made it not get corrupted by glancing at it.
But they didn’t, at least not for a long time. And it still sucks, just a little less.
The registery is much easier to break, much harder to debug and much harder to fix, UNIX config is more human-friendly, I’ll never mess with the registery again
The technology behind the registry is fine (which is what I think @VinesNFluff meant)
But it’s execution in Windows was ass
In theory, a configuration manager with DB-like abilities (to maintain relationships, schematic integrity, and to abstract the file storage details), isn’t a bad idea
Also add that registry exponantionally growing over time bad documented and not easy way to clean it up and thus as time going windows start booting up longer and longer
Nothing wrong with the Registry
It’s a different way of handling things compared to how Linux (and most unixes) does it with 18391823 text files
But it’s a perfectly functional and sensible solution for storing system configurations.
No. It was not. The concept was OK, but the execution was not. Even Microsoft didn’t know what was in there. The design was horrific. They could have used keywords, they could have had a data dictionary, they could have standardized it. They could have made it not get corrupted by glancing at it.
But they didn’t, at least not for a long time. And it still sucks, just a little less.
The registery is much easier to break, much harder to debug and much harder to fix, UNIX config is more human-friendly, I’ll never mess with the registery again
The technology behind the registry is fine (which is what I think @VinesNFluff meant)
But it’s execution in Windows was ass
In theory, a configuration manager with DB-like abilities (to maintain relationships, schematic integrity, and to abstract the file storage details), isn’t a bad idea
But the registry as it is today is pure pain
In theory having a database of configuration settings isn’t a horrible idea.
But the execution was terrible.
Also add that registry exponantionally growing over time bad documented and not easy way to clean it up and thus as time going windows start booting up longer and longer