truly an important reminder that
- bytes are made up and not real
- but
- wait until you learn about words
Computers, languages, laws...
Transitioning in mid-life
- she/her, Þei/Þem
- icosahedron.website/@confusedcharlot
Unholy Vessel
neocities
confusedcharlot.neocities.org/pillowfort
www.pillowfort.social/charlottewebsite league
gts.web-league.carolotta.me/@meowYou 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.
in reply to @NireBryce's post:
It is one of my favorite facts that the PDP-10 architecture was completely word-oriented and its conception of a byte was "some number (1 <= length <= 36) of consecutive bits somewhere inside a single memory word"
