As Flatfire mentions, another issue can arise if plugins can modify the config. I assumed config to be read-only for the software, only editable by the admins, and never by the tools themselves.
As Flatfire mentions, another issue can arise if plugins can modify the config. I assumed config to be read-only for the software, only editable by the admins, and never by the tools themselves.
I’d try to share the config space as much as possible. Options 1 and 3 make sense then.
What feels “right” to me, when using NixOS and its module system, is that all config has the same shape, and is therefor easily moved to a different section, or to a section that is shared by a subset of plugins.
Con: It could lead to bad practices like strengthening dependencies between plugins (if they hard code to use a specific config option of another plugin).
Pro: But if you can discourage that, or use “deprecated pointers” to the new location of an option, the ease of moving shared config options to a more generic level can make it easier to maintain the total configuration. Developers of the separate plugins can build on what others have already done, and even synergize functionality (add a convenient integration if they see another option configured).
If some options are “secret”, though, and you don’t want those shared, they should either be in their own config (easier), or you’d need some access control on the configuration storage/file for each plugin (more work). Allowing a plugin to have a separate file for credentials, for instance, could be a good choice.
This is still salvageable by pronouncing it as “an earl”.
I agree, and I love how it has these younger words with a vivid etymology, how it shares so many common roots with English, German, the Scandinavian languages, and a serving of French, but also sprinkles of many other languages from its seafaring and otherwise trading history. And I love the grammar rules that allow one to be precise and concise in many things (but there we must definitely bow to German).
Water bearer makes much more sense, thanks! I did notice the images where a guy carries a jug, but as a kid, I always imagined the water man to be some kind of elemental, and I never consciously challenged that idea. Haha.
In Dutch we don’t use the Latin names for zodiac signs (and we call them “sterrenbeelden”, which means “star images” or maybe “star statues”). Aquarius is “waterman”, which I guess would translate to (surprise) “water man”.
Why? Not sure, but it might be because of Simon Stevin who insisted we use Dutch words for mathematical concepts, and thought up some words like “evenwijdig” (“same distancey”) for “parallel” and “wiskunde” (“certainty knowledge”) for mathematics.
Falkor energy.
Like the Dutch “ezel” (which is the same word used in Dutch for painting-supporters which in English are called “easel”).
You can see the wololo-waves radiating from a cross if you put it in the earth.
The opening quotation marks should be on the bottom, but it’s been a while since I wrote them that way. Luckily, the wiki page (in Dutch) shows how they can be entered in three common OSes (see: unicode), so I’ll try my best to revive the correct usage again.
Also, I don’t think it is considered incorrect to use top quotation marks on a computer any longer.
Maybe he married her, instead of the other way around.
Now let’s touch on the fact that these subtitles are in Spanish.
Was the solution there to just boot an older/previous kernel?