6 ms·
I don’t think the registry is a good idea. I don’t mind every program having its own dialect of a configuration language, all under the /etc tree. If you think
by rbanffy 2y ago
I don’t think the registry is a good idea. I don’t mind every program having its own dialect of a configuration language, all under the /etc tree. If you think about it, the /etc tree is just a hierarchical key-value store implemented as files where the persistent format of the leaf node is left to its implementer to decide.
- mixmastamyk 2y agoI like what the elektra project was trying to do, but it didn't catch on. Basically put config into the filesystem with a standard schema, etc. Could use basic tools/permissions on it, rsync it, etc. Benefits of the registry but less prone to failure and no tools needed to be reinvented.
- phendrenad2 2y agoSo what's wrong with the registry if a file-based registry is okay? The registry could be an abstraction layer over a Unix /etc filesystem, after all.
- JackSlateur 2y ago"rm -rf /etc/nginx" versus "try to remember where are the miriads of random keys spread everywhere"
- alt227 2y agoThen it seems like the issue you have is how vendors are storing keys in the registry, not the registry itself. In your example, if nginx made a single node in the registry with all its keys under that then it would be just as easy to remove that single node as it would be to remove the single directory. However in the real world it is never as simple as you suggest. Linux apps often litter the filesystem with data. an app might have files in /etc and /opt with shortcut scripts in /root/bin and /usr/sbin. Config files in /home and /usr directories. Linux file systems are just as littered as windows registries in my experience, if not worse because they differ in different distros.
- nmz 2y agoLabeling, fstab is supposed to be a .tsv, what happens if I mistype something? where's the safety? Does this need to be a DSL?
- ruthmarx 2y agoI have no issue with the concept, but in practice the Windows registry is a lot more obfuscated than it needs to be. There can be trees and trees of UUIDs or similar, and there is no need for it to be so user unfriendly. Part of this might be mixing internal stuff that people never need to see with stuff that people will need to access.
- nullindividual 2y agoThat's a developer choice, not the registry in and of itself. You could just as easily have /etc filled files with GUIDs for file names. Generally, 3rd party developers don't use a bunch of GUIDs for keys. Microsoft does for Windows components to map the internal object ID of whatever they're dealing with; my assumption is for ease of recognition/documentation on their side (and generally the assumption that the end user shouldn't be playing around in there).
- ruthmarx 2y ago> That's a developer choice, not the registry in and of itself. You could just as easily have /etc filled files with GUIDs for file names. For sure, that's why I said I have no issue with the concept but rather how it's used in practice. > Microsoft does for Windows components to map the internal object ID of whatever they're dealing with; my assumption is for ease of recognition/documentation on their side (and generally the assumption that the end user shouldn't be playing around in there). That's maybe fair, but most of that stuff isn't stuff the user even needs to access most of the time. Maybe separating it out from all the HKLM and HKCU software trees would have made sense.
- nullindividual 2y agoHKLM and HKCU have specific ACLs. It wouldn't make sense to have _two_ user-modifiable registry hives and ditto for machine.
- ruthmarx 2y ago
- aseipp 2y ago> If you think about it, the /etc tree is just a hierarchical key-value store Well, you're in luck, I have good news for you -- Windows also has its own version of this concept: it's called "The Registry". You might have heard of it?
- magicalhippo 2y agoAnd since it supports variable-lenght binary values, it fully supports that "the persistent format of the leaf node is left to its implementer to decide".
- rbanffy 2y agoExcept that now it’s an opaque blob and not a text file I can use grep to find and vi to edit.
- rkagerer 2y agoThe registry would have been better if there were a stronger concept of "ownership" of the data it contains, tying each key to the responsible app / subsystem. I've tracked hundreds of software uninstalls and I would bet only about 1% of them actually remove all the cruft they originally stick in (or populated during use). The result is bloat, a larger surface area for corruption, and system slowdown. Ironically in this respect it was a step backward... When settings lived in INI files, convention typically kept them in the same place as the program, so they were easy to find and were naturally extinguished when you deleted the software. If you look at more modern OS's like Android and iOS they tend to enforce more explicit ties between apps and their data.
- alt227 2y ago> system slowdown This is often touted as a downside for the registry, and indeed a whole ecosystem of apps have evolved around this concept to 'clean' the registry and 'speed it up'. In my experience of 35 years of using windows, I have never noticed a bloated registry slowing down a computer. I have also never noticed a speed up of the system by removing some unused keys. The whole point of addresses and key pairs is that individual bits of data can be written or read without loading the whole hive. I wonder where this idea of a bloated slow registry came from?
- delta_p_delta_x 2y agoI can't quite decide if this comment is sarcasm or not.