It seems like some decisions made more sense when computers came with printers, not displays? But we inherited them.
-
-
Replying to @mwichary
Yes the entire model of using backspace for composition was tied to printing terminals, but some parts of it lived on longer because programs like less(1) go out of their way to transform backspaced underlining and bold into escape sequences
1 reply 0 retweets 0 likes -
-
Replying to @mwichary
Eric Fischer Retweeted Eric Fischer
Did you see this thread by the way? https://twitter.com/enf/status/1037138699106959360 … C's predecessor B allowed backspace in identifiers
Eric Fischer added,
Eric Fischer @enfAnother underexamined aspect of programming language history: When did the underscore become a "letter" that could be used in identifiers? C's predecessor B allowed both underscore and backspace(!) so it was probably originally there for actual underlining https://www.bell-labs.com/usr/dmr/www/kbman.pdf … pic.twitter.com/qP2xPva42kShow this thread1 reply 0 retweets 1 like -
-
Replying to @mwichary
Oh good! And Multics really embraced overstriking, with a whole input canonicalization layer to make sure programs saw the same bytes no matter what order you composed the characters in, and whether you did it with BS or CR
1 reply 0 retweets 0 likes -
-
-
Replying to @enf
Yeah, but they’re using the Wheelwriter as I/O and they’re heavily using overprinting to create the facsimiles of 1620-specific glyphs not present on Wheelwriter’s wheels.
1 reply 0 retweets 0 likes -
Replying to @mwichary
Oh yes, I saw the demo of that! Kind of a shame it's easier to do that than to get new daisy wheels made now though!
1 reply 0 retweets 0 likes
Yep! We talked about it briefly. I also sent them pointers to Unicomp and they ordered new project-specific key caps. :·D
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.