[Cthulhu_]

The registry was never an issue tbh, it's just a database that some companies decided to fearmonger about to sell you "registry cleaners".

But if I'm wrong, please do point us in the direction of known issues with the registry.

[tonyedgecombe]

It was easy to corrupt in the early days and performance was poor as it grew in size.

That was a long time ago though, it’s pretty solid now and has some benefits over storing settings in a bunch of text files such as more granular permissions.

[RiverCrochet]

Calling the registry a database makes it seem better engineered than it really is.

Running queries on the registry like SQLite? Nope. The Windows registry internally from what I've been able to read is a weird reimplementation of a file system (a trivial database I guess but a real database lets you index on things other than name). It's compact but as far as I know completely unofficially documented.

(Most data structures with unique names or ids for each data item could trivially be considered databases, but generally if you say something is a database, you typically expect to create queries more sophisticated than "select data where name is X" and also expect to be able to create or use separate indexes to support those queries.)

The reputation of brittleness and danger of the registry is because Windows stores a lot of configuration parameters there that the kernel uses as boot, but because it's not a plain text file, comments explaining what the settings do can't be right there in the same place you're editing.

[throwaway27448]

The registry absolutely is an issue—it's everything bad people make the command line out to be except ten times worse because they haven't bothered to fix it in forty years. You need to cooy and paste an incomprehensible string off the internet just to set the functionality of the caps lock key or rewire a file extension. Just straight up dogshit softwareif you weren't raised in the cult