A case against syntax highlighting (2007)
linusakesson.net
linusakesson.net
I would add a third, which I run into more frequently than either of those two:
Syntax highlighting helps in finding unterminated strings or regexes (why yes, I do write a lot of Perl). If you forget to terminate a string or a regex, a load of the rest of the file turns into string or regex colour, so it's easy to find where you made the mistake.
That, and `(2007)` seriously missing in this submission.
[1] https://www.linusakesson.net/programming/syntaxhighlighting/...
Furthermore, I'm bot sure that I even agree with the premise that syntax problems are less of an issue than semantic. The number of problems I run into that turn out to be syntax errors feels greater. Particularly thorny ones. Although that also speaks to syntax highlighting's shortcomings.
Nevertheless I enjoyed the article because it's good to rethink our assumptions.
Code highlight is a bit like all "typefaces" in this post: some part are big and bold like the sections titles, some parts are in italic. It helps you, not the other way around