In this case, I’d say it’s less about how the registry works, and more about how deliberately obnoxious Microsoft makes the experience for the sake of their agenda.
Sure if you have to deal with the registry at all, it’s “hard” but that’s casting stones from a glass house as dconf can be just as hard, and then you have the odd occasion where someone suggests dbus-send, which certainly doesn’t have room to mock registry handling as hard. The point is that most people never have to touch dconf/dbus directly to do what they want, and in Microsoft some things are deliberately obscure due to user hostile intentions.
In this case, I’d say it’s less about how the registry works, and more about how deliberately obnoxious Microsoft makes the experience for the sake of their agenda.
Sure if you have to deal with the registry at all, it’s “hard” but that’s casting stones from a glass house as dconf can be just as hard, and then you have the odd occasion where someone suggests dbus-send, which certainly doesn’t have room to mock registry handling as hard. The point is that most people never have to touch dconf/dbus directly to do what they want, and in Microsoft some things are deliberately obscure due to user hostile intentions.
Deliberately obnoxious that can be disabled by a single registry edit?
A single registry edit to a key that doesn’t exist because they wanted to obscure that it was possible.