211–220 of 282 posts
Earlier quoted context omitted.
> Developers uses powerful macs and users have old windows - the usability is different, but devs usually don't care. Works fine on my machine! Part of what QA testing should be about: performance regressions.
This is not even a regression - it has always been there, unnoticed!
Earlier quoted context omitted.
My primary monitor is the Samsung 57" 8Kx2K 240Hz ultrawide. That's the same amount of bandwidth, running over DisplayPort 2. It mostly works!
Is it actually good for productivity? The curve isn’t too aggressive? Could you, e.g. stack 3 independent windows and use all 3? Or you kind of give up on the leftmost / rightmost edges ?
With an ultra wide you lose the screen concept for managing area and it gets awful because you lose grouping windows on different screens, picking per-monitor workspaces, moving windows across screens.
Either monitors need to present themselves as multiple screens, or window managers need to come up with virtual screens to regain the much needed screen abstraction.
Earlier quoted context omitted.
Most modern games already have built-in scaling options. You can set the game to run at your screen’s native resolution but have it do the rendering at a different scale factor. Good games can even render the HUD at native resolution and the graphics at a scaled resolution. Modern OSes also scale fine. It’s really not an issue.
Games are not what I had in mind. Last time I checked, most graphics drivers didn’t support true integer scaling (i.e. nearest-neighbor, no interpolation).
The idea is to make the pixels so small that your eyes aren’t resolving individual pixels anyway. Interpolation appears correct to your eyes because you’re viewing it through a low-pass filter (the physical limit of your eyes) anyway.
Reverting to nearest neighbor at high PPI would introduce new artifacts because the aliasing effects would create unpleasant and unnatural frequencies in the image.
Most modern GPU drivers (nVidia in particular) will do fixed multiple scaling if that’s what you want. Nearest neighbor is not good though.
Earlier quoted context omitted.
This is more widespread than we like to admit. Developers writing software on 64GB M4 Macs often don't realize the performance bottlenecks of the software they write. Developers working over 1gbps Internet connections often don't realize the data gluttony of the software they write. Developers writing services over unlimited cloud budgets often don't realize the resource wastes into which their software incurrs. And…
You can nerf network performance in the browser devtools or underprovision a VM relatively easily on these machines. People sometimes choose not to and others are ignorant. Most of the time, it's just the case that they are dealing with too many things that are vague making it difficult to prioritize seemingly less important things. A number of times I've had to have a framing discussion with a dev that eventually ge…
Earlier quoted context omitted.
If you look at the Steam hardware survey, most users (as in, > 50%) are still using 1080p or below. https://store.steampowered.com/hwsurvey/Steam-Hardware-Softw...
I don't think this is contra to my original point. Nearly 50% of all users are running at greater-than 1080p resolutions, and presumably power users are overrepresented in the latter category (and certainly, it's not just the ~2.5% of Mac users pushing the average up)
> I'm honestly not sure where all these hackernews commenters with low-dpi displays are coming from
I still see 1080p fairly often on new setups/laptops, basically, although 1440p and 4K are becoming more common on higher-end desktops. Then again, 1440p at 27" or 32" isn't really high dpi.
Earlier quoted context omitted.
I wouldn't hold my breath. Competing models seem to top out around 120 Hz but at lower resolutions. I don't imagine there's a universal push for higher refresh rates in this segment anyway. My calibrated displays run at 60 Hz, and I'm happy with that. Photos don't really move much, y'know.
I imagine your mouse still moves plenty though.
The problem with using this kind of monitor for any work that others will view on their own monitors is that your perception of what looks good will be way off. For example, it's clear that a lot of the Rust UI framework developers have been working on Macs for the last few years. The font rendering on many of those look bad once you plug them into a more normal DPI monitor. If they hadn't been using Macs with Retina…
This is more widespread than we like to admit. Developers writing software on 64GB M4 Macs often don't realize the performance bottlenecks of the software they write. Developers working over 1gbps Internet connections often don't realize the data gluttony of the software they write. Developers writing services over unlimited cloud budgets often don't realize the resource wastes into which their software incurrs. And…
The problem with using this kind of monitor for any work that others will view on their own monitors is that your perception of what looks good will be way off. For example, it's clear that a lot of the Rust UI framework developers have been working on Macs for the last few years. The font rendering on many of those look bad once you plug them into a more normal DPI monitor. If they hadn't been using Macs with Retina…
That’s not the problem of using this monitor for creating the work, that’s the problem of not also using a more typical monitor (or, better, an array covering the common use cases, but which is practical depends on whether you are talking about a solo creator or a bigger team) for validating the work.
Just as with software, developers benefit from a more powerful machine for developing, but the product benefits from also being tested on machines more like the typical end-user setup.
Earlier quoted context omitted.
Also, it's not only about the screen resolution. Developers uses powerful macs and users have old windows - the usability is different, but devs usually don't care. Works fine on my machine! Had reported many issues where to reproduce they needed to enable 10x throttling in the browser. Or use a Windows machine.
> Developers uses powerful macs and users have old windows - the usability is different, but devs usually don't care. Works fine on my machine! Part of what QA testing should be about: performance regressions.