if UTF-8 is so good how come there's no—
Blue Ears Ultimate Otter
- Eng: They/þei Esp: -x/-e/-a
- telegram.me/BlueEarOtter
➡️ https://bsky.app/profile/blueearotter.bsky.social
[Water/Fusion]
"Blue Ear (Left)" + "Blue Ear (Right)" + "Otter"
Nonbinary ☿ . 34. Chicanx. Asexual Panromantic. furry. Astrophotografur/Prof. of Astronomy. Mexican Folk Harpist (Mariachi and Jarocho mostly). Music, games, crochet, horror, etc. HRT: 2022-05-15
Atk: 4,500
Def: 3,800
You must log in to comment.
in reply to @iliana's post:
sudden vibes of "M. Crispin, now that's a name I haven't heard in a long time"
finally! something to do with those parity bits we never bothered to actually implement error correction hardware for ( this might be a personal problem but also it keeps happening lmao )
bummed it's just 8 bit payloads with a continuation bit, all the neat little tricks that make utf-8 a prefix-coded self-synchronizing encoding that sorts lexically are missing
from THE YEAR OF OUR LORD TWO THOUSAND AND FIVE
what nonet machine could POSSIBLY still be relevant in 2005???
yeah I opened this and pogged for exactly long enough to notice the publication date :(
It's my favorite AFD RFC just because while it may be a gag it's a perfectly reasonable technical proposal that could be implemented on a real 18- or 36-bit machine with little trouble, complete with reasonable sample code.