Fx*

an interface from the ’00s*

based on its* use

Errors can give away that a human typed something, but knowing proper grammar, spelling, and syntax of English is totally neutral—if not to be somewhat expected from a native speaker/typer with a lifetime to learn the language they speak (especially if we consider how many Anglophones are monolingual + educated + have access to technology like spell check meaning there is little excuse for not having English mastery).

In my education, I got a public apology from a teacher letting the class know they tried to dig up proof of plagiarism in my persuasive papers, but for the first time proved themself incorrect on a plagiarism hunch. Humans are capable of writing well.

The inconsistent 2 spaces after “LOL.” shows this comment was from a human.

Think of the phrase: about music. “90’s music” would imply music from specifically 90 (probably 1990 where we assume the writer was lazy about the initial apostrophe)—possessive form. “’90s music” uses ’90s as an adjective for the entire decade—and with the preceeding apostrophe makes it clearer 19 is omitted. 1 year versus 10 years as a big difference. Using an apostrophe in the right place clearly removes the ambiguity.

It was an error. It happens, and too many people do it so next time maybe you won’t with a good habit being formed.

One man’s pedentry is another man’s pet peeve. This is a syntactic error that isn’t just a typo but a misunderstanding of the mechanics of apostrophes.

Really. Apostrophes are used for possession & contractions (not making words plural). In this case, you are omitting the 19 from the decade starting at 1990. What is plural is the years inside that decade, meaning the 10s place. All to say, it is 100% ’90s*.

in the late ’90s*

I think you need to run the service yourself

🫸🫷

all big OSs*

slidge-whatsapp gateway for XMPP

They’re in their 60s*

But lovely story ❤️

Nvidia GPUs*

The ’90s*

1000s*

No need to ignore history. Older ALGOL versions used several now-Unicode operators. A lot of language support it. You have most of the APL + its dialects (such as BQN), theorem provers like Agda and LEAN 4, functional languages supporting Unicode Preludes like Haskell and PureScript, MATLAB, Mathematica, RPL, Raku, Julia, AppleScript, and of course the TI BASICs. Not to mention ≠ is what is used in general math(s) & handwriting. All this to say, it’s more common than you are leading on.

https://en.m.wikipedia.org/wiki/ALGOL_68

ALGOL 68, mother of all the C-likes, has ≠. There ace quite a few languages support Unicode such as ≠. What is not equals then? Exclamation mark + equals? Forward slash + equals? Tilde + equals? Less than + greater than? Equals + forward slash + equals. What is more clear than all of those aforementioned options from ‘modern programming languages’? 2260 ≠ Not Equal To. Type what you mean, specifically. Your programming language doesn’t support it? Your language is hurting clarity.

Since we are talking about terminals, you are probably talking about abuse of ligatures