Yes. The basic error checking provided by something as simple as different colours for reserved words, defined variables, strings, etc, is extremely useful.

More developed syntax highlighting which knows about methods or functions that are in scope vs out of scope, variabkes that sre not defined in this scope, etc, are another layer of utility.

I get used to "for" being a certain shade of blue. When it is not blue, there is something wrong. If it is green, I have an unclosed string somewhere. If it is red, I have an unclosed block interfering with scope. If it is underlined, I have put the "for" where the parser was expecting an identifier.

Color coding syntax makes code jump off the page for many of us. Does it for you?

Bracket and parenthesis highlighting alone is invaluable.

My style is Obsidian, with a dark background, yellow/orange quoted text, blue variables, grey comments, bold white operators, white block comments. Ported from VI to N++ for a unified experience.

I tried turning off syntax highlighting for a while. I actually liked it better. But at the time I was programming in Clojure, where there isn't much syntax, and you just read your code as a tree of tokens mapped to abstract ideas. In Lisp my favorite use of syntax highlighting is honestly to decrease the opacity of parentheses.

That's kind of interesting, now that I think about it. I wonder if in other languages I'd prefer coding in one color but with all errors and open brackets in red. Does anyone know something like this for Vim?

I would argue that it does. It helps me spot stupid errors that I might have to hunt for later if it wasn't for seeing the pattern of colored syntax highlighting.

I find it helps in grasping the gross structure of a piece of code, which lets me know where to focus my attention. Also highlighting strings has saved my butt a few times.