felbane

This isn't true any more, and it's mentioned in the article. Sodium is at least equivalent to - and on pace to surpass - the energy density of Lithium. It's already being used in passenger cars in the Far East.

A haiku:

"It's not DNS."
"It couldn't be DNS."
It was DNS.

I tend to block at the user and community level, my only instance block is feddit.de and that's only because I don't speak German and those folks are such prolific posters it felt like I was touring central Europe every time I'd go to the All feed.

Blocking what you're not interested in is the second best part of Lemmy, IMO.

I always found this argument funny because how would you use pronouns for someone whose gender you do not know? They. It's they. E.g. you are given the sentence: Jordan went to the store to buy apples. And you want to ask a followup question regarding how many, you reply: How many apples did they buy?

And that's not how English was taught to me or 99℅ of the population (including English as a second or third language) 20+ years ago. Singular they was only used for situations where the gender (read as superficially visible sex) was factually unknown. You see a forgotten umbrella and never saw who forgot it: "Somebody forgot their umbrella." As soon as you only got a glimpse on the person forgetting it you would make a guess about he/she.

You're contradicting yourself here. You're saying you were taught to use singular they when gender is unknown, yet claim that "How may apples did they buy" is wrong based on how you were taught English.

Does it matter whether gender is unknown or just unresolved? Not really, singular they is clearly intended to be a gender neutral pronoun and works in any situation where gender is ambiguous. It's not wrong for people to adopt it as a pronoun to refer to themselves any more than it is for a trans man to adopt "he/his" or a trans woman to adopt "she/hers."

At best your refusal to use it makes you sound like one of those people who gets offended at the word "literally" gaining a colloquial meaning that differs from its original definition. At worst, it presents as transphobia to claim "language purity" as the reason to be so adamantly against something that the trans community has largely adopted.

lmao gottem

No, I was specifically responding to "only KDE calls it meta."

Only when viewed from the north.

Every front-end guide, despite modern HTML/CSS3/ES6+ being completely viable for building an entire web application without dependencies: "first, install npm and npx and npy and npppp2 and then run 'npz create-huge-boilerplate-folder'. Now go edit arbitrarily_named_file.yaml to add requirements a, b, and banana. Now you can edit path/to/hidden/entrypoint.jsx to return 'Hello, World!' and then run 'npz bloated-dev-http-server' and navigate to http://127.0.0.1:9001/index to view it! Simple!"

I think the issue is that you need to understand who your users actually are. Documentation for a library intended to be used by a reasonably competent software engineer is going to have different requirements vs documentation for a cli utility aimed at Arch btw Linux users vs documentation for a program to help Grandma organize family photos.

If you throw a terminal command at Grandma she's going to panic and call her grandchild. If you put instructions for extracting a tarball in your library docs the programmer is going to get bored and skip ahead.

Amazon is no better. Go look up the correct parameter format required to set a compliance lock on an object in S3 via the API. Now try it yourself. Surprise!

It's not just kde, for example the backronym for Emacs is "esc meta alt ctrl shift"

The most famous is never get involved in a land war in Asia, but only slightly less well known is this: Never go in against a septuagenarian when blindness is on the line!