It’s all too* expensive

Fx* on Linux

🫸🫷

all big OSs*

slidge-whatsapp gateway for XMPP

found in Fx*

the source of Fx*

They’re in their 60s*

But lovely story ❤️

Pretty sure it was fsck, but I could be wrong

F smart TVs*

Fx* with ArkenFox

’80s* band

sells NFTs*

Nvidia GPUs*

The ’90s*

1000s*

FOSS projects are often worth their salt

a lot*

than* these AI bots

APL programmers usually use an APL keyboard layers. Some people use Compose. Vim offers digraphs. Some editors can replace with a macro. Input is a solved issue, but the outputs can often either be more clear for reading either for lack of ambiguity such as the ligatures or in information density as seen especially in the APLs (see a 1975 demo) (hence Chinese writing taking up less paper space being more information dense). The ligatures themselves are still taking up the same physical character space since that is how ligatures operate. I believe the goal here is to achieve something similar with ligatures, except taking an opentype hack instead. If you believe ligatures are more readable, then everyone should be seeing these concocted symbols on any device or font, which Unicode offers without the hacks or ambiguity.

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.