3 ms·

It's cute idea but, feels distracting. Maybe a nicer color scheme would work better.

ori_b 11y ago
To be fair, I've started to feel the same way about syntax highlighting in code. I've slowly moved to only highlighting 2 things: String literals and comments.
- gkya 11y ago
  I'm nowadays using a theme in Emacs where everything is black on white and keywords and comments are bold, whereas code regular. I'm happier with this than syntax colouring nowadays. I've also removed some colour from Org, namely headlines are bold and black. Again, I guess the less the colours the better here. I use colours with parens, they're pale by default, then highlighted with highlight-parenthesis mode, denoting nesting via tones of red. I'm even doing some html-css-js-m4 work for a relatives business website nowadays, and I did not miss highlighting even with such complex mess, instead, I'm happier.
- marssaxman 11y ago
  I like to have language keywords accented too, since that helps me scan the shape of the code without having to read it closely, but yes - most of the benefit is just in knowing what context you should read the characters in.
- Mikhail_Edoshin 11y ago
  Same here. I do not highlight anything though: just white text on black background.
kpil 11y ago
I found it to be very distracting. The reading process stopped on every colour change - especially punctuation and conjunctions, etc. Larger blocks of cited text might work.
- yxhuvud 11y ago
  You find that if you scroll down, but yes, darkening the interjections is not helpful.
  - kpil 11y ago
    I saw it. I could not really tell if it was good - as it was now with the dark text. I can't help to think that this was done by someone that does not read that much. Younger people seems to prefer videos instead of READMEs, and I have not really understood why until I saw somewhere that speedreading skills apparently have been falling drastically among young people. I mean why look at a video for 30 minutes to see if a tool or framework is worth trying, when you can scan the equivalent text in 30 seconds.

ori_b 11y ago

To be fair, I've started to feel the same way about syntax highlighting in code. I've slowly moved to only highlighting 2 things: String literals and comments.

gkya 11y ago
I'm nowadays using a theme in Emacs where everything is black on white and keywords and comments are bold, whereas code regular. I'm happier with this than syntax colouring nowadays. I've also removed some colour from Org, namely headlines are bold and black. Again, I guess the less the colours the better here. I use colours with parens, they're pale by default, then highlighted with highlight-parenthesis mode, denoting nesting via tones of red. I'm even doing some html-css-js-m4 work for a relatives business website nowadays, and I did not miss highlighting even with such complex mess, instead, I'm happier.
marssaxman 11y ago
I like to have language keywords accented too, since that helps me scan the shape of the code without having to read it closely, but yes - most of the benefit is just in knowing what context you should read the characters in.
Mikhail_Edoshin 11y ago
Same here. I do not highlight anything though: just white text on black background.

kpil 11y ago

I found it to be very distracting. The reading process stopped on every colour change - especially punctuation and conjunctions, etc. Larger blocks of cited text might work.

yxhuvud 11y ago
You find that if you scroll down, but yes, darkening the interjections is not helpful.
- kpil 11y ago
  I saw it. I could not really tell if it was good - as it was now with the dark text. I can't help to think that this was done by someone that does not read that much. Younger people seems to prefer videos instead of READMEs, and I have not really understood why until I saw somewhere that speedreading skills apparently have been falling drastically among young people. I mean why look at a video for 30 minutes to see if a tool or framework is worth trying, when you can scan the equivalent text in 30 seconds.