I hear the GOAT is even better.
I hear the GOAT is even better.
No need. Only the average Dutchman. And he’s only average, so…
Something like tac | head | tac
, I guess? Yes, that’s a valid use case indeed :)
I mean… it’s nice that it exists and all, but I can’t really think of many useful usecases.
Heh, no, but they do have a nice set of man pages and other documentation online. I prefer NixOS. Easier keeping track of configuration, easier rolling back of (and experimentation with) new stuff.
I don’t think their “No” was a disagreement, but a confirmation of your second line. https://ell.stackexchange.com/questions/88502/how-to-agree-with-a-negative-statement-with-yes-or-with-no Sometimes, language can be a tricky tool to wield.
That fills me with determination.
Was the solution there to just boot an older/previous kernel?
Probably understood that in the wrong direction. Ze (eng. phon.) would be spelled more like “sie” (ger. phon.) and would sound like “the” with a German accent. They would become either dey (eng. phon.) or zey (eng. phon.), spelled like “deej” or “seej” (ger. phon.), or even without the y (or j) at the end.
I think. I’m neither native German or English.
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.
That is an interesting source. Thanks for the link!
That’s why you feed that flame once in a while.
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.
Is there a generic (non-brand) name for these boiling-water faucets? (That’s not a mouthful like “boiling-water faucets”). I think we call them quookers here, which is also a brand name, and I slightly dislike that practice. I mean, “brand name for generic thing” is very common, but the brands and things differ per country, so it’s like a layer of jargon to decipher.