Excuse me, sir, this is a well-respected barbershop.

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.

Yet.

👏👏👏👏

I like that I can hear that omitted space there.

git was designed to be decentralized. Everyone can (technically, but it is not too hard to set up if you have some affinity with servers) fork/clone another git repository and serve it up. It has built-in ways to synchronize with any other server. In fact, that synchronizing is what most developers do when they use git.

Of course, that would make it harder to know which repository has the “official” version, but in a way, that is maybe also a benefit of decentralisation. Knowing what code is authentic can be done by signing the commits.

The hubs that we see, are usually a combination of git and a way to serve the code, along with documentation, roadmap, bug tracking, automatic testing and building and the resulting binaries in a visually pleasing way. That does not need to be a part of decentralizing the code, and it is not the only way to do it.

Some of that can also be done with git built-in tracking of files, and the building and testing can probably also done in other locations, as long as there are files describing how to do that bundled with the code (which practically all projects already do).

Sourcehut (https://sr.ht) is one hub that helps developers use simpler tools for those workflows, and I think that’s a good place to find some inspiration.

Might not be a useful plugin, but fans of Terry Pratchett might like the GNU Terry Pratchett idea. For librewolf I use this slightly updated add-on which fixes some minor issues (source available).

Heh, thanks. I did just look up what people on StackExchange thought about it, and in short: both are correct, although the word originated as a mass noun (uncountable).

I was guessing that the intended usage would be “email messages”. And I would compare it to (snail) mail. You can get a lot of letters, but it is still a lot of mail.

Thanks! I’ve used emails as a plural of email for a long time, referring to the messages. Not a native speaker, maybe it’s something Dutch people do with some loanwords. Never softwares or the (more recent) codes, though.

I will never not read LTT as Lews Therin first, of whom, as a lover of both FOSS and EotW, I definitely prefer being reminded.

E: my brain forgot that the series is called WoT. EotW is just the first book, indeed. But I’m rambling very much off topic here.

At least the sawhorse resembles a horse :)

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.

I guess it is a matter of how “fluent” you are in the language. With some foreign languages, e.g. when I started learning a bit of Japanese, I could recognize some kanji, understand some bastc sentences, but still had no idea what it would sound like. Maybe it’s similar to that. We get good at recognizing patterns and interpret them just enough to accomplish what we need, and if we haven’t had any use for “knowing exactly what it sounds like” (maybe just enough to recognize we are missing some notes while playing), we save the energy needed to learn more.

But a conductor would definitely need to know what it should sound like (or how they would want the orchestra to make it sound), so it is part of the interpretation of the pattern.

Same for lords patrician and other intra-audiophiles.