Ethan Blanton on Nostr: This is your periodic reminder that the Model 33 #Teletype – the device on which ...
This is your periodic reminder that the Model 33 #Teletype – the device on which #Unix and the C programming language were largely developed – HAS NO CURLY BRACKETS.
The pictured source code is printed on a Model 35 Teletype, which is a different mechanism but uses the same ASCII '63 character set. Note that the Unix TTY driver (V6, in this case) knows this, and prints { and } as \( and \), respectively.
Somehow I never learned this in DECADES of learning about early Unix.
Published at
2024-01-11 02:48:37Event JSON
{
"id": "3d6cd90fbb78de15614de808b7efacbef20df93196b3d07e9b310d1ac8f3813e",
"pubkey": "0bb270c3dc6e41ec03b2c921e1681ce3ba6db31d157e6e477fcef8f5a104a7fc",
"created_at": 1704941317,
"kind": 1,
"tags": [
[
"t",
"teletype"
],
[
"t",
"unix"
],
[
"proxy",
"https://social.sdf.org/users/elb/statuses/111735034153249103",
"activitypub"
]
],
"content": "This is your periodic reminder that the Model 33 #Teletype – the device on which #Unix and the C programming language were largely developed – HAS NO CURLY BRACKETS.\n\nThe pictured source code is printed on a Model 35 Teletype, which is a different mechanism but uses the same ASCII '63 character set. Note that the Unix TTY driver (V6, in this case) knows this, and prints { and } as \\( and \\), respectively.\n\nSomehow I never learned this in DECADES of learning about early Unix.\n\nhttps://social.sdf.org/system/media_attachments/files/111/735/019/862/505/973/original/e16fc725d7dcf61f.jpg",
"sig": "208cef64ab05b676453e73add0b5c9421b795ebc0f213e4d8436b87ed5325e3eb9b86adbb4d2319c87fbc0e51f12bd394c8a331679afabe74187b8e0712d1143"
}
