4 ms·
We're really good at parsing code, thanks to languages designed to be easy to read and to our style guides (unless we don't have one, of course). Highlighting k
by dystroy 7y ago
We're really good at parsing code, thanks to languages designed to be easy to read and to our style guides (unless we don't have one, of course). Highlighting keywords is uselessly tiring for the eyes IMO.
What matters most is to separate code from what's not code and which doesn't follow the same rules: comments and string-like literals.
In my vim color scheme (https://github.com/Canop/patine https://github.com/Canop/patine) I only have three colors: one for code, one for comments, one for strings, and I find reading the code easier and less tiring this way.
- z5h 7y agoYes yes yes! For a long time this three color style was my philosophy. It's all you need. I'm currently (with new laptop) doing a thing where I try to install/customize as little as possible. This means not using that philosophy, but not because it didn't work.
- mikelward 7y agoMe too. Plus a color for errors, and one for line numbers and other non-code parts of the UI. https://github.com/mikelward/conf/blob/master/vim/colors/basic.vim https://github.com/mikelward/conf/blob/master/vim/colors/bas... And a similar theme I wrote for vscode. https://marketplace.visualstudio.com/items?itemName=mikelward.theme-plainlight https://marketplace.visualstudio.com/items?itemName=mikelwar...