Turning off the syntax highlighter

To each its own of course, but for the life of me I cannot imagine why I would want to turn off syntax highlighting. If it helps you being more productive and understand code better, then please continue, but it's not for me.

With highlighting, I can easier understand the structure of sentences in the source. Keywords stand out and I can quickly scan the code for the parts I am interested in. If I suspect something is wrong in the definitions I scroll up until the color of the code tells me I am in the definition part of the source. If I make a typo, the words don't color so it tells me I made an error so I would not want to live without it. To me syntax highlighting is the best thing since sliced bread.

Won't venture to disagree with others' results, but turning off syntax highlighting would be detrimental to me. Due to my dyslexia, I rely on it heavily to help me visually parse code, and catch typos early.

Well, at least you have good taste in music! :)

Last time I didn't have any syntax highlighting while coding, it was C64 BASIC, and I was 10. I have generally seen my code improve and my errors be easier to find as the degree of syntax assist tooling I've used has increased. Today, I use (all hooked into Atom) prettier, eslint, and syntax highlighting (Nord theme)... Not a whole lot of syntax errors go undetected.

So to me, this would be catastrophic advice.

How can you say:

Getting more focus on the work, that mean, more productivity
Read/understand the code better, and even faster

Without a parallel you working on the same thing over that period of time? This is bogus click bait.

I think, with code highlighting, you really need to evaluate what is being highlighted. Then you will suddenly notice that it doesn't really make sense to highlight everything.

For example Java keywords highlighting is not necessary - you can live with having them bold. Highlighting every code symbol (function, variable) also kinda misses the point. However knowing which variables are static and which are constants - is actually useful.

I don't think a developer should code without highlighting - that's a bad idea. But you should evaluate what highlighting you really need.

I'm trying this out. Also trying out VIM since I delayed it quite some time!

I'm curious about your status line style and that music playing thingy. Would you mind sharing it? I love the style of it :)

Your screenshot includes bold keywords and dimmed comments, so I assume you're either rolling your own or using a minimal syntax highlighting scheme, rather than actually turning it off?

You say "Getting more focus on the work, that mean, more productivity" but the only coloured thing on your screen, which immediately grabs attention, is a clock and a song title, both of which are totally unrelated to work (unless you're coding a bot that writes metal...)

Haha, I can’t believe some of these responses... seriously people? I learned to code long before syntax highlighting was a thing, and honestly, while I do use it today, I like a very tame color scheme for the most part. To me it seems like everyone should basically create their own theme, because we all think differently, and we all react to colors and other distractions differently.

Anyway, here’s to experimentation and exploration!

Am I too late to mention syntax highlight is NOT off in your screenshot? I mean, it's grayscale, ok, but still.

I tried this a thousand times. I change my color schemes all the time, it's a little less boring, since we now have to code with plugins and linters telling us what to do.