It’s a definition from a well-respected global standards organization. Can you name a source that would provide a more authoritative definition than the ISO?

There’s no universally correct definition for what the ≈ symbol means, and if you write a paper or a proof or whatever, you’re welcome to define it to mean whatever you want in that context, but citing a professional standards organization seems like a pretty reliable way to find a commonly-accepted and understood definition.

Sure! See ISO-80000-2

Here’s a link: https://cdn.standards.iteh.ai/samples/64973/329519100abd447ea0d49747258d1094/ISO-80000-2-2019.pdf

“Approximately equal” is just a superset of “equal” that also includes values “acceptably close” (using whatever definition you set for acceptable).

Unless you say something like:

a ≈ b ∧ a ≠ b

which implies a is close to b but not exactly equal to b, it’s safe to presume that a ≈ b includes the possibility that a = b.

“Nah, your fingernails don’t need a trim. If she can’t handle your adult man’s untrimmed fingernails inside her, she does not deserve to have sex with you.”

Hair that’s long and overgrown can cause problems just like long fingernails can cause problems. Keeping them trimmed so they don’t is just being considerate of your partner.

But that’s not what TypeScript does. The joke in the meme doesn’t really even make sense.

A better analogy would be you have a basket that’s explicitly labeled “Fruit” and TypeScript complains if you try to put laundry detergent in it because you said it’s supposed to be a basket of fruit.

This meme was clearly made by someone who doesn’t use or understand TypeScript.

I prefer just calling everything I eat the flesh of whatever it came from. Tomato? Flesh. Lettuce? Flesh. People? Flesh.

What if you soak them in high fructose corn syrup first?

Towels honestly dry you off SO much better when they’re washed with no fabric softener. It’s worth an extra wash to do towels separately

I noticed Google also changed Maps recently for multi-stop directions so it only calculates routes once you’ve added all the stops instead of after adding each stop. The only rationale I could think of for doing that would be to reduce computation costs.

Seems like they’re going around and trimming compute and network costs wherever they can without significantly impacting user experience.