Syntax highlighting is a waste of an information channel
This kind of nibbles at the edges of the longstanding question: Whether source code is best represented as a linear document.<p>Because historically, that was true for the obvious reasons of pragmatism; you could put it on a punchcard, print it to paper, save it to a file all using the same character encoding and rendering methods, and when we went to interactive editing that didn&#x27;t change: half of the joy of plaintext is that you can select, copy, paste, search and modify in mostly standard ways across many tools.<p>Syntax highlighting is incrementally in line with this paradigm since there&#x27;s only one syntax for the language(syntax extension and mixed-language documents aside) and it too follows a linear order, although it also recognizes that an AST exists. But as you get into stuff like code folding, Intellisense and other IDE-like features, deviations emerge. More of the selections deal with symbolic meanings(declarations, types) and not really the tokens or the characters they consist of, and only incidentally the delimiters of the AST.<p>But - when we try to fully re-envision it and express these other concepts directly we tend to end up with something that is unfamiliar, a bit clunky and alienating(most graphical languages). So the accepted developments always seem to come in these little ideas that are mostly-optional add-ons.<p>Chuck Moore did use semantic color as a language feature in ColorForth, but his specific goals lean towards a holistic bootstrapping minimalism, so I haven&#x27;t seen it taken up elsewhere.