Agreed on this. Especially with the return keyword argument presented in the same article.
An assertion of correctness relating to a matter of taste is, ironically, going to be trivially falsifiable. Even though I found myself personally agreeing with most of what the author had to say (for my tastes)! I definitely want to try lifting the visual importance of comments.
I don't think keywords need to have a distinct color, though. It's enough to just use the base color and make it bright and/or bold.
I kind of agree, but I think it might be ok to turn off keywords sometimes, unless broken. Highlight "retunr" in reverse video.
Agreed with almost everything the author had to say, but not this. Hard disagree. In my view, keywords are the single most important thing to highlight. I'd be ok without anything else. Keywords sketch the structure of the program in most languages. The thing I want my eye drawn to, in the case of top-level definitions, for example, is the keyword. It's the predictable anchor as I'm scanning a long series of definitions. The identifiers are not: some are long, some are (very) short.
And how do I understand the control flow of my program? I look at keywords. If I want to read the condition, I have to find the condition. But all the conditions look different. What's the reliable way to spot them? The predictable 'if' that precedes each one, without fail.
My eye is a parser. It needs to recognize tokens. But some tokens are easy to confuse: keywords look just like identifiers.