4 ms·

Here is a slightly more readable version that's not white-on-white, half-pixel-thick text: https://lkml.org/lkml/2018/6/5/769 https://lkml.org/lkml/2018/6/5/769

by mcbits 8y ago

kuschku 8y ago
Reading on a 400dpi 300nits screen in a slightly dark room, the lkml link hurts the eyes significantly more. Reading on a shitty 96dpi 100nits screen from 2004 in a bright room, the lkml link is the more readable one. Another situation of the eternal issue of "we need a web standard for specifying relative contrast", not "make everything blinding #000 on #fff".
- AstralStorm 8y ago
  Or perhaps do not specify any dumb colours, let the browser do its job of presenting things. Oh wait, you know you can switch CSS to default layout? Perhaps the browser could use an option to still apply layout but ignore formatting and colours.
  - mort96 8y ago
    The problem is that browsers are generally really terrible at presenting text in a readable and good-looking way. Compare http://motherfuckingwebsite.com/ http://motherfuckingwebsite.com/ and http://bettermotherfuckingwebsite.com/ http://bettermotherfuckingwebsite.com/ - most people would agree that the second is significantly easier to read. I really wish browsers' default formatting could be trusted to be as readable as possible, but alas.
- mcbits 8y ago
  Also useful would be a standard way to normalize the apparent size and weight of different fonts so the fallbacks won't look like shit. Apparently my problem is more with the Courier font bundled with Ubuntu, as replacing Courier on that page with just about any other font makes it somewhat readable (still a "disabled" gray, but at least visible).
- systoll 8y ago
  By the CSS2 standard, #000 and #FFF are sRGB colours, with #000 targeting 0.2cd/m^2, and #FFF targeting 80cd/m^2, with adjustments for ambient light level. With CSS4, you can choose other colour-spaces instead. The web standard is there, but so long as 99% of users have setups which emit 300+cd/m^2 and say they're emitting 80, you can't do much with it. The push toward HDR displays gives us another chance to 'get it right' wrt calibration, but a quick google search of 'HDR washed out' demonstrates why it's an uphill battle to get consumer displays to be honest.
  - kuschku 8y ago
    Yeah, it's a major issue — and with CSS there's also no easy way to set HDR colors either. Hell most displays nowadays don't even do sRGB, which was defined as the colorspace and contrast of an average 1990 CRT.

Here is a slightly more readable version that's not white-on-white, half-pixel-thick text: https://lkml.org/lkml/2018/6/5/769 https://lkml.org/lkml/2018/6/5/769

by mcbits 8y ago

Here is a slightly more readable version that's not white-on-white, half-pixel-thick text: https://lkml.org/lkml/2018/6/5/769 https://lkml.org/lkml/2018/6/5/769

kuschku 8y ago

Reading on a 400dpi 300nits screen in a slightly dark room, the lkml link hurts the eyes significantly more. Reading on a shitty 96dpi 100nits screen from 2004 in a bright room, the lkml link is the more readable one. Another situation of the eternal issue of "we need a web standard for specifying relative contrast", not "make everything blinding #000 on #fff".

AstralStorm 8y ago
Or perhaps do not specify any dumb colours, let the browser do its job of presenting things. Oh wait, you know you can switch CSS to default layout? Perhaps the browser could use an option to still apply layout but ignore formatting and colours.
- mort96 8y ago
  The problem is that browsers are generally really terrible at presenting text in a readable and good-looking way. Compare http://motherfuckingwebsite.com/ http://motherfuckingwebsite.com/ and http://bettermotherfuckingwebsite.com/ http://bettermotherfuckingwebsite.com/ - most people would agree that the second is significantly easier to read. I really wish browsers' default formatting could be trusted to be as readable as possible, but alas.
mcbits 8y ago
Also useful would be a standard way to normalize the apparent size and weight of different fonts so the fallbacks won't look like shit. Apparently my problem is more with the Courier font bundled with Ubuntu, as replacing Courier on that page with just about any other font makes it somewhat readable (still a "disabled" gray, but at least visible).
systoll 8y ago
By the CSS2 standard, #000 and #FFF are sRGB colours, with #000 targeting 0.2cd/m^2, and #FFF targeting 80cd/m^2, with adjustments for ambient light level. With CSS4, you can choose other colour-spaces instead. The web standard is there, but so long as 99% of users have setups which emit 300+cd/m^2 and say they're emitting 80, you can't do much with it. The push toward HDR displays gives us another chance to 'get it right' wrt calibration, but a quick google search of 'HDR washed out' demonstrates why it's an uphill battle to get consumer displays to be honest.
- kuschku 8y ago
  Yeah, it's a major issue — and with CSS there's also no easy way to set HDR colors either. Hell most displays nowadays don't even do sRGB, which was defined as the colorspace and contrast of an average 1990 CRT.