lvxferre

At least Mint has an OEM install; on the first boot after installing the system, it asks you to create a user (plus language, layout etc.). I never used it though, but I expect other distros to have a similar feature.

My bad, and thanks for the info! I'll correct my comment, I kind of rushed checking the etymologies.

China comes from sina/sino. I don’t remember where this comes from. Sanskrit?

Odds are that both were independently borrowed from Sanskrit चीन / Cīna:

• China: Sanskrit, then Persian, Portuguese, English. By then Portuguese likely still had the [tʃ] "tch" sound.
• Sina: Sanskrit, then Persian, Arabic, Greek, Latin, English. Arabic converted Sanskrit [tɕ] into [sˤ], then Greek into [s].

Note: dunno in English but at least in Latin "Sina" (often Sinae, the plural) refers specifically to southern China. The north is typically called Serica (roughly "of the silk").

A bit of both.

I don't typically build things just for the looks, but once I'm building them I take aesthetics into account. Just the usual - picking a style that fits what I'm building (e.g. cottagecore for villager-powered farms, industrial for Thermal mods, steampunk for Create etc.), design the thing in creative mode, then build something that fits the terrain OK to host my contraption.

back to Sanskrit, being the grand daddy of English

Sanskrit is more like English's uncle than granddaddy: English is from Proto-Germanic, and both Proto-Germanic and Sanskrit are from Proto-Indo-European.

English likely got the name from Portuguese, "Japão" *[ʒä'pɐ̃ŋ] (see note). I don't think that it's from Dutch "Japan" because otherwise the name would end as "Yapan", as Dutch uses a clear [j] ("y") sound.

In turn Portuguese got it from either Malay or some Chinese language. I think that it's from Cantonese 日本 jat⁶ bun² [jɐt˨ puːn˧˥]. Portuguese has this historical tendency to transform [j] into [ʒ] (the "g" in "genre"), and to mess with any sort of nasal ending.

The name in Chinese languages can be analysed as meaning simply "Sun origin". Because it's to the east of China.

In turn, there are a few ways to refer to Japan in Japanese:

• 日本 / Nihon - it's a cognate of that Cantonese jat⁶ bun². Except that it uses the Japanese rendering of Wu Chinese words.
• 日本 / Nippon - same as above, with a slightly more conservative pronunciation (Japanese converted a lot of [p] into [h]).
• 大和 / Yamato - it's metaphorically referring to the whole (Japan) by one of its part (the Yamato province, modern Nara).
• 日の本の国 / Hinomoto-no-Kuni - poetic and dated name. 日/hi = Sun, 本/moto = origin, 国/kuni = land, の = an adposition**. So it also means "land of the origin of the Sun". The big difference here is that all words used are inherited from Old Japanese, so there's no Chinese borrowing involved.

*note: that [ŋ] is reconstructed for around 1500 or so (Nanban trade times), given the word was also spelled Japam back then. A more typical contemporary pronunciation would be more like [ʒä'pɜ̃ʊ̯].

**the best way I know to explain Japanese の/no is that it works like a reversed English "of": in English you'd say "origin of Sun", in Japanese you'd say "Sun no origin" (hi no moto = 日の本). I only remember this because of Boku no Hero Academia, because "boku no" = "of I" (my).

Shameless plug to [email protected] . This sort of question is welcome there.

Latin already did a bloody mess of those suffixes:

• if you were born in Roma, you'd be romanus ("Roman")
• if you were born in Eboracum (modern York), you'd be eboracensis ("Yorkese")
• if you were born in Gallia (roughly modern Belgium and France), you'd be gallicus ("Gallic")

In turn those suffixes used to mean different things:

• that -anus was originally just -nus. Inherited from Proto-Indo-European *-nós; you'd plop it after verbs to form adjectives.
• that -icus was originally just -cus; from PIE *-kos, but you'd plop it into nouns instead.
• nobody really knows where -ensis is from but some claim that Latin borrowed it from Etruscan.

Then French and Norman inherited this mess, and... left it alone? Then English borrowed all those suffixes. But it wasn't enough of a mess, so it kept its native -ish suffix, that means the exact same thing. That -ish is from PIE *-iskos, and likely related to Latin -cus.

And someone from Afghanistan is an Afghan? How did the word get shorter not longer? 🤔

There's some awareness among English speakers that "[$adjective]istan" means roughly "country where the [$adjective] people live", so the suffix is simply removed: Afghanistan → Afghan, Tajikistan → Tajik, etc.

That -istan backtracks to Classical Persian ـستان / -istān, and it forms adjectives from placenames.

In turn it comes from Proto-Indo-European too. It's from the root *steh₂- "to stand", and also a cognate of "to stand". So etymologically "[$adjective]istan" is roughly "where the [$adjective] people stand". (inb4 I'm simplifying it.)

Also, why is a person from India called an Indian, but the language is called Hindi? This breaks my brain…

Note that India doesn't simply have different "languages"; it has a half dozen different language families. Like, some languages of India are closer to English, Russian, Italian etc. than to other Indian languages.

That said:

• "India" ultimately backtracks to Greek Ἰνδός / Indós, the river Indus; and Greek borrowed it from Old Persian 𐏃𐎡𐎯𐎢𐏁 / Hindūš. That ending changed because it's what Greek does.
• "Hindi" comes from Hindi हिंदी / hindī, that comes from Classical Persian هِنْدِی / hindī. That hind- is the same as in the above, referring to the lands around the Indus (India), and the -ī is "related to".

Now, why did Greek erase the /h/? I have no idea. Greek usually don't do this. But Latin already borrowed the word as "India", showing no aspiration.

Philippines --> Filipino? They just saw the “Ph” and decided to use an “F”? 🤔

So, the islands were named after Felipe II of Spain. And there's that convention that royalty names are translated, so "Felipe II" ended as "Philip II" in English. And so the "Islas Filipinas" ended as "Philippine Islands".

...but then the demonym was borrowed straight from Spanish, including its spelling: filipino → Filipino.

Note that this mess is not exclusive to English. As I hinted above, Latin already had something similar; and in Portuguese for example you see the cognates of those English suffixes (-ese/-ês, -an/-ano, -ic/-ego... just no -ish).

Except that for Portuguese simply inheriting the Latin suffixes wasn't enough, you got to reborrow them too. So you end with etymological doublets like -ego (see: Galícia "Galicia" → galego "Galician") and -co (see: Áustria "Austria" → austríaco "Austrian").

Then there's cases where not even speakers agree on which suffix applies, and it's dialect-dependent; e.g. polonês/polaco (Polish), canadense/canadiano (Canadian).

Besides afegão vs. Afeganistão (Afghan vs. Afghanistan), another example of a word where the demonym is shorter than the geographical name is inglês vs. Inglaterra (English vs. England). But it's the same deal: -terra is simply -land, so people clip it off.

There's also the weird case of "brasileiro" (Brazilian), that -eiro is a profession suffix. Originally it referred to people extracting brazilwood, then the country name was backformed from that.

Talking about Chemistry eggcites me.

Help. What?

The Latin stuff? "Hail Brutus, Longinus, Cimber, and others. They were liberators and heroes - and Caesar a filthy tyrant".

If you mean the on-topic instead: Bluesky does lip service to decentralisation, while Zuckerberg is openly fascist.

In this case the alternative is to post in the most active one. By then the user should already have a good grasp on which one it is, unless they post mindlessly.

That said I like cross-posting. Sometimes I see 3~4 people talking to each other in the different threads - but they're approaching the subject from a different angle, because of the specificities of each comm.

Subscribe to all of them, duh. Problem solved.

And then when posting you simply cross-post. Or stick to the most active one. By then you already know which it is. (Unless you post mindlessly on whatever comm you find, without even lurking a wee bit before doing it. Then you're probably shitting Reddit and should stay there instead of shitting Lemmy.)

The author is a muppet babbling about what they don't know.

TL;DR: here's a better guide. 90s video included if you don't want to read shit.

An extra tip is to add some baking soda (sodium bicarbonate) to the boiling water. This will increase the boiling temperature of water

For kitchen purposes, the effect of dissolved salts in the boiling point of water is negligible. For baking soda you'd need to add more than 1tbsp for each cup of water, to raise it by a whole bloody degree. And even if the effect was relevant you'd achieve the same with any other solute, even table salt.

The actual reason you might want to add some baking soda (or vinegar, or salt etc.) to the boiling water is because it denatures proteins, so if one of your eggs cracks while boiling, the white solidifies faster; hopefully sealing the crack off. This means cleaning less egg white gunk from your pot. (The shape of the boiled egg is probably ruined anyway. I generally throw those in - eat your failures so they won't haunt you.)

Once you boil the eggs for a particular amount of time (which we will discuss later), you have to rapidly cool them. This ensures that we utilize the difference in thermal conductivity between the different layers of the egg. The results is a shell that is easier to remove.

Thermal conductivity is irrelevant here. What could matter is thermal expansion: things get smaller when cold, but at different ratios, but even then I don't think thermal expansion plays a big role here.

The actual reason why "throw them into cold water" is good advice threefold:

1. because it stops the cooking process immediately, so you get a more consistent result. Carryover cooking is a thing.
2. because the egg white gets firmer, so you're less likely to rip it apart.
3. because peeling hot things is a literal pain.

For #2 and #3 you could also fridge them overnight. I don't bother, I'm usually too eager to eat them.

There is some amount of moisture trapped between the shell and the albumin. It prevents the sulfur and iron inside the yolk from forming iron sulfide, which is the grayish color we often see on over-boiled yolks.

The moisture has jack shit to do with this, but point #1: you're preventing the egg from getting overcooked. And guess what, it's cooking that breaks sulphur off the proteins! That's why, for example, you'll get green/grey yolks if you cook the eggs for too long, even if you dump them into cold water afterwards.

Time is another important factor. If you want to achieve a particular style of boiled egg you need to boil it for a certain temperature. I usually eat hard-boiled eggs and 11-13 minutes after I have added the eggs to the boiling pot works well for me. If you want to do 9, you can experiment with 9 as well. That could lead to a jammy yolk and the white being solid. It results in eggs which have good visual, Instagrammable looks.

A picture is worth a thousand words:

Taken from J. Kenji López-Alt's guide on perfect boiled eggs. Way better guide than the one in the OP, showing another way to do this: start with already boiling water, gently land the eggs into the water with the help of a spoon, wait, remove them from the water, profit.