11 ms·
I have been using my same vim workflow now for twenty years, ever since I switched from Visual C++ 6... and, at the time, I configured some of the colors in vim
by saurik 6y ago
I have been using my same vim workflow now for twenty years, ever since I switched from Visual C++ 6... and, at the time, I configured some of the colors in vim to match parts of what I had been previously getting from Microsoft's editors. I thereby have had largely consistent colors for like, "a quarter of a century". Despite thinking a lot about syntax highlighting for various reasons, it honestly never once occurred to me--before reading your comment--that some (many?... _most_?!?) software developers don't have consistent syntax highlighting even across different languages much less through their career. OMG.
- remus 6y agoIt may well just be me, but what I find valuable about syntax highlighting isn't the colours per se, but the differentiation between different kinds of token in the language (comments, keywords, argsb etc.) Therefore I don't really notice the individual colours, I notice when the colour changes.
- npsimons 6y agoThis is what I'm talking about. It's that comments are one color, function/method/class/struct definitions are another, keywords are another. And it's the same, no matter what language I'm programming in. Heck, I can open up a language I haven't touched in years (or ever) and just start to get a feel for the structure based on the syntax highlighting alone.