10 ms·
Uff, lots of files. My first idea after reading your comment was to consolidate the settings into two key=value files (simplified INI files): One for defaults,
by tqkxzugoaupvwqr 4y ago
Uff, lots of files. My first idea after reading your comment was to consolidate the settings into two key=value files (simplified INI files): One for defaults, one for custom settings.
- forgotmypw17 4y agoIt's a couple thousand files, nothing a modern filesystem can't handle.
- imtringued 4y agoThis is how the node_modules blackholes were created on earth. One package at a time until they reached critical mass.
- forgotmypw17 4y agoIt's definitely a tradeoff, but I decided to do it this way for ease of maintenance. Most of the settings are 0/1 or a one-line string, but a few are multi-line. This also allows me to store templates under the same tree, which is where most of the code lives. Because I use one call for getting and setting a config setting, I can probably rearchitect it in the future to e.g. a key-value store. But for now, it just makes it so easy to maintain from the shell, and to create overlay themes, and so many other possibilities that I'd never dreamed of before.