9 ms·
The job of the registry is to be a reliable structured storage with access control and other features. It is not responsible for the things that go into itself.
by ksk 8y ago
The job of the registry is to be a reliable structured storage with access control and other features. It is not responsible for the things that go into itself.
Here is the API.
https://msdn.microsoft.com/en-us/library/windows/desktop/ms724875(v=vs.85).aspx https://msdn.microsoft.com/en-us/library/windows/desktop/ms7...
Could you point out which one of these doesn't work as intended?
- jacquesm 8y agoIf you put together a structure like that and leave the sordid details up to the implementer and you supply a mostly confusing example as the set shipped with the OS, and subsequently mess it up even further with your own application installs you own the mess.
- nitrogen 8y agoAn upvote isn't always enough, so I just want to say I support your holistic view of engineering and find the "not a bug, not my problem" approach detrimental to the broader success and acceptance of technology in society.
- ksk 8y agoI'm unable to extract anything specific from your comments. Are you still talking about the registry or about something else? Its cathartic to vent, but the registry is not the source of your frustration.
- jacquesm 8y ago> I'm unable to extract anything specific from your comments. That's ok.
- thomastjeffery 8y agoThat's because it's about the bigger picture.
- ksk 8y agoOkay.. call me small-picture-minded but I much rather prefer - "I press a button M and Feature X doesn't work when I choose option Y" - over "Feature X is terrible at its job"
- thomastjeffery 8y agoWhen a platform is purposefully incompatible with another platform, that effectively devalues the other platform for users. Unless you are totally convinced that your chosen platform is the only one that matters, this behavior is a problem.
- Too 8y agoThe problem is not that they don't work as intended, the problem is what is intended. You can't just throw application developers an API like a system wide key value store and expect the whole worlds ecosystem of applications to organize itself around it. Android and iOS solve this much better by sandboxing application settings within the app. Uninstalling the app is guaranteed to remove any traces of it (unless you give access to "all files and photos"), whereas on windows there is always some remains.
- ksk 8y agoIts just a database. Using the registry is not a requirement for any app. They can store their configuration in a text file, they can store it in the cloud, they can do whatever they want, they can even create a C:\etc and store it there :) Sure, there exist badly behaving apps that don't clean up after themselves when they're uninstalled. Windows gives apps the freedom to choose their own method of installation, but some vendors abuse those freedoms. I don't quite know what the OS is supposed to do about that. Windows already does an insane amount of work trying to keep buggy apps running, something that macOS or iOS or Android or Linux don't. The fundamental goal of any consumer OS should be making sure that the software a user purchased continues to work. >Android and iOS solve this much better by sandboxing application settings within the app. So, multiple users on a device = separate settings = multiple app installs? That might work OK for consumer devices, but won't really fly in the IT world.