I don't really "buy" the reasoning[1] behind "no syntax highlighting" either, BUT I turned off syntax highlighting (in vim/neovim in my case) about 5 years ago

I don't really "buy" the reasoning[1] behind "no syntax highlighting" either, BUT I turned off syntax highlighting (in vim/neovim in my case) about 5 years ago (that was ~15 years into programming full time) and haven't looked back. I just don't miss it at all. At first I wanted to see what it was like to not have syntax highlighting because I realized I had never questioned the need for it. I found out I really liked not having it! I can't put my finger on why exactly, and this is the first time I think I've ever written a single word on the subject (ie, I'm not trying to convince anyone else to try it). But I also use "light mode" (white background, black text) in my terminal, editor, etc, so... take all this however you will :) (In reference to the topic at hand, I've tried seriously using acme, and although its "elegance" is attractive, I wasn't able to make it stick. I'll still open it or sam up every once in a while, and vis (https://git.sr.ht/~martanne/vis https://git.sr.ht/~martanne/vis) is an editor I always have in the back of my mind to try to use more.) [1]: The reasons against syntax highlighting in the article seem to be 1. it hides ugly code, 2. it's possible to waste a lot of time on configuring your colorscheme, 3. (not in the article, but) the old "do you syntax highlight prose? I didn't think so". I don't find 1 or 3 to be convincing, and wasting time on a colorscheme... whether it's a "waste" or not depends on your own preferences and circumstances.