DEV Community

Discussion on: acme/acme2k: A lesson in sane IDE defaults.

Collapse
 
okdewit profile image
Orian de Wit

I passionately disagree with the notion that syntax highlighting is a bad thing. Those who argue against it always use the worst colors as an example of why it would be bad.

A good color scheme turns comments into background information, and highlights the structure of the code — with good colors, your eyes can quickly isolate all the method names from a class, and combined with an IDE which understand the language it should identify unused imports and variables. A random color scheme is indeed not useful, but using color to signal structure and semantics is extremely useful.

Collapse
 
tux0r profile image
tux0r

I passionately disagree with the notion that syntax highlighting is a bad thing.

It was not meant like that. Personally, I made the experience that I can work without it in languages which are not JavaScript or C#, but I can also see why some people wouldn't touch an editor without syntax highlighting.

In VS Code (one of the text editors I'm using - yes, I'm definitely using too many editors...) I have a very simple theme: Comments are light grey, code is dark grey, keywords are italic.