3 ms·
I don't think the 'terminal' model of UI gets enough attention. I don't know why that is, perhaps it is a feeling that it is the "old" way to do things and so n
by ChuckMcM 8y ago
I don't think the 'terminal' model of UI gets enough attention. I don't know why that is, perhaps it is a feeling that it is the "old" way to do things and so not a source of good ideas.
Xerox's XDE had a very nice terminal. It could use proportional fonts and you still had precisely formatted text for code. It was not as fast as a VT100 or an xterm which relied on monospaced fonts. But that was the root of the issue.
Terminals conflate "formatting" and "content" in the worst way possible, there is content that "is" formatting (whitespace). This closely mimicked how typewriters did it but they did it that way not because it was "best" but because it was "possible" given the mechanics of building lines of type without a bunch of lead letters.
It is insidious how that in band content/formatting mixing of ASCII and then later ISO-Latin-x drove compromises in editor and text manipulation tool design. But here we are.
I wrote a pretty printer for come code once that pulled apart the format from the content and it would print out source code with a nice proportional font (I think a2ps(1) could do this too at some point) and I admit that the code "looks wrong" in that form but I also have to admit that it only looks wrong because I'm not used to seeing it in that form. It is harder to read when things like parenthesis fade into the text because they are so much thinner, but this is again the design vs eyeball sorts of trade-off.
When I read this bit what I heard was "Gee, it would be really awesome if some designer could capture the flow of terminals with a modern set of capabilities." But that XDE terminal? Dave Curbow, who was with Xerox Business Systems, once tracked down how many function calls had to be made before the glyph ever hit the screen and it was a lot. It made it hard to run efficiently on the hardware of the time (great when you can code new microcode, less useful on CPUs without that capability).