KM 30 Hz does contribute to the strain, but not significantly.
I am using Linux comfortably
Markus It's a very old system: Dell OptiPlex 755, Core2 Duo E7300 @ 2.66 GHz. Disabling compositing for Xfce means going to "Applications - Settings - Window Manager Tweaks - Compositor" and to uncheck "Enable display compositing". I use the Firefox browser, which has the version 102.6.0esr. By default, it does not use hardware acceleration unless it is explicitly enabled in about:config. I don't think the default settings cause additional eye strain.
I also disabled font anti-aliasing and installed the Microsoft TrueType core fonts (known from Windows XP), which unlike other fonts still look good when anti-aliasing is disabled. A downside is those fonts haven't been updated in years, missing modern Unicode characters (like the search icon in this forum's search bar for example). Disabling anti-aliasing may or may not have an impact, I'm not sure about that yet.
KM Try the Bitstream Vera fonts too, I like the mono one in particular. They're also fully hinted and from the same era. https://download.gnome.org/sources/ttf-bitstream-vera/1.10/
8 days later
I'm looking for other options as Windows 2015 LTSB isn't cutting it for me. Anyone recommend a comfortable distro I should try?
bz12 Pop OS comes to mind.
EyeDiscomfortCertificate just tried and it was uncomfortable for me.
bz12 Oh, you mean visually uncomfortable? Yes, font renedering is worst on Ubuntu based distros. The most likable font renderer for my taste are on OpenSUSE and Manjaro.
11 days later
KM Disabling anti-aliasing was definitely the key to solving my eyestrain problems on all the operating systems I use (Windows, Ubuntu, Android). It took me months of searching and looking down many blind alleys before I discovered that anti-aliasing was the cause of my problem (Why is this so hard? Why is there so little discussion of this as a cause of eystrain in mainstream media?) Months more research to find reliable, comprehensive ways to disable it but once I did - bliss. I can now use my devices for as long I want with zero eyestrain.
- Edited
bz12 Which OS are you using?
George357 Why is there so little discussion of this as a cause of eystrain in mainstream media?) Months more research to find reliable, comprehensive ways to disable it but once I did - bliss. I can now use my devices for as long I want with zero eyestrain.
I wrote on this forum about certain forms of font antialisting and potential negative effects a number of years ago.
ryans It's pretty simple in Ubuntu as long as you have basic knowledge of using the terminal / command line. I wrote a guide on how to do it in the ubuntu forum a while back in response to someone's question. Here is the page address:
copy and paste that into your address bar and scroll down to the answer beginning with:
'I had the same issue in Linux Mint 19.2…'
and then follow the instructions there.
- Edited
bz12 I've written up a guide that explains how to disable anti-aliasing in Windows 10. It took me a bit longer than expected to write, hence the delay in replying. It's too long to enter here so I've put it up on another site. Here is the link:
https://superuser.com/questions/1762568/how-to-disable-font-smoothing-anti-aliasing-in-windows-10
Don't be put off by the length, most of that is just my wordy explanations. The actual technique is quick and easy to apply.
The same cannot be said for disabling anti-aliasing in Android, that's altogether more challenging.
There is no setting to 'turn off' anti-aliasing in Android, nor is there an app for that. Anti-aliasing is hardcoded 'on' deep in the Android code, the only way to turn it off is to modify that code.
My method relies on replacing one of the core Android system files with one that I've modified to block the system call that turns on anti-aliasing. On most Android phones this is impossible, you can only do it on phones that have the option to unlock the bootloader (xiaomi/poco, google pixel, motorola, oneplus, sony, possibly some others). Furthermore, my method will only work on phones that are running close to stock Android (ie no or minimal modifications from standard Google Pixel Android). Once your bootloader is unlocked you will have to 'root' your phone by installing software called Magisk and then use Magisk to install a small piece of code containing my modified system file. All that requires you to connect your phone to a PC and use special software called adb and fastboot to manipulate your phone and install certain files.
That's just a brief summary of what's involved. A detailed step-by-step guide would be far longer. You may already have decided it's way too much trouble which is fair enough. I only did it because I had to. Ten minutes of reading Android's anti-aliased text is enough to make my eyes hurt, more than thirty minutes and discomfort turns to burning pain so the choice for me was: turn off the anti-aliasing or don't have a smartphone.
If you want the full step-by-step guide, post a reply and I'll start writing, but it might take me a while.
George357 thanks for the dedication. I will try with Windows tomorrow. As for Android, I don't think my issues are solely text related, so it's no big deal. I alone don't want to take any more of your time unless there's several people here interested. Plus I don't have a compatible device atm but possibly in the future.
15 days later