4 ms·
I think you're missing parent's point. The benefits of staring at text all day with >30yo eyes also applies to Linux. I use Arch and Fedora on high-dpi displays
by vox_mollis 10y ago
I think you're missing parent's point. The benefits of staring at text all day with >30yo eyes also applies to Linux. I use Arch and Fedora on high-dpi displays and I'd sooner give up programming than ever return to ~72dpi.
Parent isn't talking about most apps, they are referring to terminals and IDEs, for which use case high-dpi is absolutely critical, and outweighs the occasional inconvenience of poor scaling outside those apps.
- malkia 10y agoBut that's where I disagree, especially when comes to terminals. I'm so used to seeing the pixels, that it doesn't bother me, but even then hinted anti-aliasing helped quite a lot to solve this. What I'm really missing (and hence my heavily opinionated answer) is that there are lot of people that might just started coding on higher DPI monitors/devices, and to them going back would be terrible. I started on Apple ][ :)
- rayiner 10y agoI'd hate to go back to the eye-strain inducing fuzzy low-res CRTs we had to tolerate back in the day. I can look at my rMBP screen all day without getting a headache.
- msbarnett 10y ago> What I'm really missing (and hence my heavily opinionated answer) is that there are lot of people that might just started coding on higher DPI monitors/devices, and to them going back would be terrible. It has nothing to do with that. I learned to program on a 72DPI sony trinitron screen in the 90s. UltraHD is strictly a less eye-straining experience, "what I grew up on" be damned.
- mark-r 10y agoI haven't seen anything approaching 72dpi since 1024x768 stopped being common, most modern displays are north of 100dpi. It's still far too low though. We've been held back far too long by the OS and app makers inability to adjust to a reasonable resolution.