The original poster’s point is precisely that it isn’t “ethnic” because it’s originally in Chinese (民族) without a direct obvious translation. The linked translated text has a note on their chosen translation:

“民族- ethnic, ethnicity. Official translations are fond of translating this as nationality, which is confusing because it can confuse statehood/citizenship with ethnic identity. In most situations, we use forms of ethnic.”

https://www.chinalawtranslate.com/en/ethnic-unity-and-progress-law/#Notes

For what it’s worth, Firefox’s translator (bergamot) also translates this as “National Unity”. The definition on pleco seems to imply more of an ethnic nation, as in a nation of peoples as opposed to a nation state.

Translation is not a one-to-one mapping between words. The act of translating a text will always distort the meaning a bit. It’s good to consider what may have been lost in the process of translation, especially when a contentious translation seems to align with a position that is geopolitically convenient.

For those that need a translation:

“You have got to be shitting me”

“I am in fact not shitting you, my dude. It is very disappointing that this is real.”

I’d bet that they symlinked /ubuntu to the server’s home root - probably for continuity with some previous file structure. It sure looks silly, but I’m sure the reasons for doing it were pretty reasonable.

I don’t know anything about being an electrician - commercial or otherwise, so I’m curious to hear your side.

When all those people go to working remote, it’s not like they’re no longer in need of electricity. Presumably their home demand is higher and we might even see people adding new office spaces to adapt their home. Maybe the public grid needs to change to support it? Won’t this mean that there will just be a different type of demand for electricians?

Are there reasons this would be less attractive to electricians? Pay, job security, or something else?

For anyone who’s curious, this is the state of discussing this feature: https://github.com/helix-editor/helix/discussions/8572

I’m not an authority on the helix ethos, but I’ve contributed a bit and hung around long enough to have a good read on their stance on most topics. The project is still young and managing the growing pains of getting a lot of traction relatively early. I think the devs value keeping the maintenance footprint small to keep the project sustainable.

The philosophy of helix’s design is to be a more convenient kakoune, not necessarily a vim. vim is much more widely known, so that analogy springs up more often, but this idea of using piping out to an external command for most operations comes from kakoune.

For features that would introduce significant maintenance overhead, may jeopardize the performance of a more common workflow or where the design goals are still maturing, the team tends to push such suggestions toward being developed as plugins when that system is added. I get the impression that they see the value of this workflow, but would prefer to see it battle tested as a plugin first.

A few animal-inspired names that I think have a nice ring to them

• Dodopedia (extinct like Mastadons, similar vowel rhythm to “wiki”)
• Hippopedia
• Komodopedia

You can substitute “at least 10 years ahead” as stated in the second sentence of the article quoting US senators.