Akronymus
Joined 7 years ago
Joined 7 years ago
A user can set custom settings, and those settings may or may not have a value assigned to them. For example, one setting is optimization level, another option is a debug flag.
You want to have a unified interface to get information about settings, queried through some intermediate system. (lets just say it is limited to querying specific settings, rather than getting the entire list, due to legacy constraints in this case) Because for some settings you just care about them existing and for others you care about the actual value, you have to differentiate between a setting that contains something, a setting that contains nothing, and one that doesnt exist.
That feels like the covid amnesty thing to me. Say the previous "version" of x was insane and we should just blanket forgive and forget about it. Kind of a rejecting all responsibility.
(besides, i dont think there is a woke 1/2 in the first place IMO)
Anyways, much happier now that I no longer use it.
Ive got to disagree there, the mistake is in it not being readonly accessible. Monitoring fridges in such a setting is one of the few times it actually does make sense to put online readonly.
Edit: nvm thats already in the guidelines
Need a few math operations? pull those in, instead of an entire math lib, for example.