elch
As for the name, the acronym ASCII comes from the 1963 version (American Standard Code for Information Interchange). Later in 1966, ASA became USASI, and the official name was changed to USASCII, with ASCII as an acceptable alternative abbreviation. Later still, in 1969, USASI changed its name once again to ANSI, and an attempt was made to rename it ANSCII, but this did not catch on, and ASCII returned as the official name.
https://www.sensitiveresearch.com/Archive/CharCodeHist/X3.4-...
Because eight rather than six bits are used to represent a. character, up to 256 possible characters could be represented in the Extended Binary Coded Decimal Interchange Code (EBCDIC) shown in Figure 7. Except for certain teleprocessing equipment, the code that makes use of characters is either EBCDIC or an eight-bit extension of a seven-bit code proposed by the International Standards Organization.
[1] http://bitsavers.informatik.uni-stuttgart.de/pdf/ibm/360/GC2...
https://www.graalvm.org/latest/reference-manual/native-image...
In the past you could use e.g. Excelsior JET.
16GB RAM (4GB+Up to 12GB Extended RAM)
Use ⌘ + + until you get the line length you like.
But of course he was wrong about 1991-2026:
The days of non-raster stuff are numbered, though sheer momentum will carry it to the end of the decade.
And about AT&T as the same year (1984) they introduced BLIT terminal:
The fundamental tension in UNIX that I think AT&T doesn't understand is that everyone is going to have a bitmap.
What I disagree with is the idea that C++ was developed completely independently of C (and Unix) - it originated at Bell Labs and was initially just an extension of C with classes. If you looked at the document I linked to, you would see that Bjarne Stroustrup thanks Dennis Ritchie in it for being a source of good ideas and useful problems. I don’t think I need to explain who Dennis Ritchie was for C and Unix.
Of course, these were just examples to show that a computer terminal didn’t have to - and doesn’t have to - be like a VT100 or similar. And I realize that nowadays, when we hear the word "terminal," we tend to think of something like a VT100. Especially since the Linux (kernel) includes emulation for something like that.
However, historically, the first devices to be called computer terminals (and to enable interactive operation) were typewriters and teletypes. That is why one of the names given to newer CRT terminals was "glass teletypes." To distinguish these terminals from their predecessors, they were also referred as video terminals (VT) or video display units (VDU) etc.
Note that in addition to built-in VT102/VT220 emulation, xterm also includes built-in Tektronix 4014 emulation, which, to use your terminology, is a graphics terminal.
But on the topic, IMHO those "text terminals" represent the lowest common denominator, and using them as a user interface causes the least friction compared to true GUIs. For example, after booting Linux, I can basically start using those TUI programs right away without having to install or configure a graphical environment (X11 or Wayland). Remote computing also causes less friction and can essentially be used out of the box.
And TUI programs, like GUI programs, also make it easier and faster to explore compared to programs that run exclusively in CLI mode.
Personally I regret that Plan9-style computing and Oberon/ACME user interfaces didn’t become mainstream...