3 ms·

Let's have a "registry".

by olgeni 10y ago

IshKebab 10y ago
Yes, KDE and Gnome both have registries. Just because Windows' registry is hard to manually edit doesn't mean they are a bad idea. Look at how much better Windows' GUI configuration tools are than anything on Linux. They all use the registry.
- markdown 10y ago
  > Just because Windows' registry is hard to manually edit doesn't mean they are a bad idea. That's not the problem with Windows registry.
  - wfunction 10y ago
    >> Just because Windows' registry is hard to manually edit doesn't mean they are a bad idea. > That's not the problem with Windows registry. What is?
    - markdown 10y ago
      https://blog.codinghorror.com/was-the-windows-registry-a-good-idea/ https://blog.codinghorror.com/was-the-windows-registry-a-goo...
      - wfunction 10y ago
        Your link explicitly says you're wrong, though. Read it. It says: > My life would be a heck of a lot easier if per-application settings were stored in a place I could easily see them, manipulate them, and back them up. Like, say... in INI files. > The registry is opaque and binary. As much as I dislike the angle bracket tax, at least XML config files are reasonably human-readable, and they allow as many comments as you see fit. Now look at the comment you replied to: > Just because Windows' registry is hard to manually edit doesn't mean they are a bad idea. You said that's not the problem with the registry, but your own link says that's exactly the problem with the registry...
- jstimpfle 10y ago
  Registry has some serious practical problems. How do I easily list, or copy to another machine, the settings for application X? For technical users these are the most important operations. I know how to view or copy a text file... An associated problem is that the registry accretes trash that is never weeded out (and it's hard to weed it out). Also at least in former times it was slow (partly because of the trash thing, probably partly because of the implementation, partly because of the centralised design).
  - ComodoHacker 10y ago
    >How do I easily list, or copy to another machine, the settings for application X? with reg query, reg export and reg import commands, respectively. Or with a few clicks in the GUI, if you prefer.
  - Godel_unicode 10y ago
    Right-click that program's config hive, export. Move file to new system, merge. I did this very frequently before PowerShell got amazing support for the registry (seriously, it's the best. Tab completion of registry values in get-childitem if you supply a registry path). > ...accretes trash If your app doesn't remove it's old settings when uninstalled how is that a problem for the registry to solve? It happens with /etc also. > hard to weed it out Search for the hives if you don't know where they are. Right-click the hives in question, delete. Registry usability got leaps and bounds better in Windows 7, and again in Windows 10. Most registry problems you hear about are holdovers from the bad old days (XP and older).

Let's have a "registry".

by olgeni 10y ago

Let's have a "registry".

Yes, KDE and Gnome both have registries. Just because Windows' registry is hard to manually edit doesn't mean they are a bad idea. Look at how much better Windows' GUI configuration tools are than anything on Linux. They all use the registry.

markdown 10y ago
> Just because Windows' registry is hard to manually edit doesn't mean they are a bad idea. That's not the problem with Windows registry.
- wfunction 10y ago
  >> Just because Windows' registry is hard to manually edit doesn't mean they are a bad idea. > That's not the problem with Windows registry. What is?
  - markdown 10y ago
    https://blog.codinghorror.com/was-the-windows-registry-a-good-idea/ https://blog.codinghorror.com/was-the-windows-registry-a-goo...
    - wfunction 10y ago
      Your link explicitly says you're wrong, though. Read it. It says: > My life would be a heck of a lot easier if per-application settings were stored in a place I could easily see them, manipulate them, and back them up. Like, say... in INI files. > The registry is opaque and binary. As much as I dislike the angle bracket tax, at least XML config files are reasonably human-readable, and they allow as many comments as you see fit. Now look at the comment you replied to: > Just because Windows' registry is hard to manually edit doesn't mean they are a bad idea. You said that's not the problem with the registry, but your own link says that's exactly the problem with the registry...
jstimpfle 10y ago
Registry has some serious practical problems. How do I easily list, or copy to another machine, the settings for application X? For technical users these are the most important operations. I know how to view or copy a text file... An associated problem is that the registry accretes trash that is never weeded out (and it's hard to weed it out). Also at least in former times it was slow (partly because of the trash thing, probably partly because of the implementation, partly because of the centralised design).
- ComodoHacker 10y ago
  >How do I easily list, or copy to another machine, the settings for application X? with reg query, reg export and reg import commands, respectively. Or with a few clicks in the GUI, if you prefer.
- Godel_unicode 10y ago
  Right-click that program's config hive, export. Move file to new system, merge. I did this very frequently before PowerShell got amazing support for the registry (seriously, it's the best. Tab completion of registry values in get-childitem if you supply a registry path). > ...accretes trash If your app doesn't remove it's old settings when uninstalled how is that a problem for the registry to solve? It happens with /etc also. > hard to weed it out Search for the hives if you don't know where they are. Right-click the hives in question, delete. Registry usability got leaps and bounds better in Windows 7, and again in Windows 10. Most registry problems you hear about are holdovers from the bad old days (XP and older).