But the need for color seems too strong to fight with pure rationality. Perhaps it's enough that adding a little color to an environment we spend a significant amount of our lives in makes us happy. Since I have no taste, garishness doesn't bother me :)
Here's an example of color being used in a relatively staid place -- and paying for itself: https://plus.google.com/110440139189906861022/posts/UqyUZdqP...
Hopefully these considerations will be subsumed by new research by Bret Victor or Rune Madsen (http://vimeo.com/61113159).
For now, here's my preferred syntax highlighting, with just a dash of color in most usual places, but two colors for comments: http://i.imgur.com/H1h7M.png. (Why 2 comment colors? http://akkartik.name/post/2012-11-24-18-10-36-soc has the scoop.) Notice how the left pane is C++ and the right pane is my toy lisp, and the syntax kinda harmonizes.
Disagree, it helps confirm you typed it correctly when you are trying to, and that you've named something incompatibly when you aren't. Thereby very likely preventing syntax/name errors before they happen.
Yes, highlighting language keywords is like capitalizing or bolding the unstressed words in English:
THERE IS A book ABOUT programming ON THE table.I use syntax highlighting, but I use very mellow colors that do not distract. The example given out in Akesson's article is a complete eyesore, however many text editors are like that and it's not that simple to change the color scheme in all of them.
I believe syntax highlighting can also spoil you if that's all you're used to. It is a good exercise to write and maintain some code in raw format, occasionally.
Personally I think it's enough just to highlight the reserved keywords and comments.
http://www.linusakesson.net/programming/syntaxhighlighting/
I still think it is nutty.