3 ms·
> I don't understand all the talk about performance - programs should be reading config once on start up and that's it. non-microsoft programs were not intende
by naikrovek 4y ago
> I don't understand all the talk about performance - programs should be reading config once on start up and that's it.
non-microsoft programs were not intended to use it when it was designed. the performance considerations are for windows itself.
Microsoft's guidance has always been for third party applications to manage their own configuration in whatever way they choose, so long as it isn't the registry.
developers ignore that, use the registry, and blame Microsoft for keeping the registry around even though Microsoft promises to do everything they can to keep things backwards compatible.
- CamperBob2 4y agonon-microsoft programs were not intended to use it when it was designed. the performance considerations are for windows itself. That's not what I remember. Someone at Microsoft had a personal jihad against application-specific .INI files scattered all over the place, and came up with the registry as a centralized solution. I still use .INI files myself, although Microsoft did successfully manage to get me to stop putting them in the executable directory where they belong. :-P