Hacker News new | ask | show | jobs
by stonewareslord 1600 days ago
> Quite a lot of us at least overlap with that. Basically all FE web or GUI dev, any end-user image/video processing, pretty much anything that puts graphics on a screen that aren’t UI SDK builtins.

I completely disagree, except for high end picture or video production. I have used way too many websites that clearly only work well on large, nice displays. Most end users of anything will not have the same high quality expensive monitor/computer that's being suggested.

I remember reading some article about someone who used an old i3 processor on a 4:3 laptop screen or something, knowing that if his code is slow for him, it's slow for his users. I think this mindset is genius and should be more common. Take MS Teams for example. It's like their devs have only ever tested on a gigabit link M1 and it's painful for the other 99.9% of people who use it.

So if you want to get a nice setup for yourself, then you should. But you should not do it for your clients, and if you do, you should understand your users will not have machines like yours.

1 comments

Upthread I also stressed the importance of using lower quality displays to account for that aspect of real world usage. The point of having high quality displays to support users who don’t is to be able to reliably understand what’s being displayed in the first place. If you’re working at low fidelity you can only address the users who have the same system flaws you do.