News for hackers. Stuff that matters.

A comment on Why is a registry file called a “hive”? (2003). Parent comment

Re:Why is a registry file called a “hive”? (2003) by nicce on Wednesday May 11, 2022 @05:33AM (#31337643)
> You can drop a program into a directory and run it. If you want it to integrate with the OS or DE, you need an installer to configure it in the centralized location. No difference there between Windows and Linux.

This applies only for minority of the programs. There are many programs which simply refuse to work or crashes because some entry is missing from the registry.

[ Parent | on HN ]
Re:Why is a registry file called a “hive”? (2003) by dogma1138 on Wednesday May 11, 2022 @06:26AM (#31337948)
The minority of programs actually do the latter, and it’s not about the OS but about the fact that the program was designed to be reliant on the registry.
[ Parent | on HN ]
Re:Why is a registry file called a “hive”? (2003) by nicce on Wednesday May 11, 2022 @06:29AM (#31337974)
Of course it is the fault of program, but as design registry is thought to be always there, self-evident, so it is partially the problem. It encourages to rely on it totally.
[ Parent | on HN ]
Re:Why is a registry file called a “hive”? (2003) by dogma1138 on Wednesday May 11, 2022 @12:46PM (#31342496)
It doesn’t mean that it’s used correctly.

The registry is intended to be used for interacting with system configuration or for system wide settings. E.G. registering a new file extension or a URI scheme.

It’s not an application data store that’s what appdata is there for.

[ Parent | on HN ]