10 ms·
I’m not willing to give up my 3840x1600 ultrawide. That real estate is now non-negotiable to me. So to improve the dpi I’ll need 7680x3200, and at 120hz I don’t
by nsxwolf 6y ago
I’m not willing to give up my 3840x1600 ultrawide. That real estate is now non-negotiable to me. So to improve the dpi I’ll need 7680x3200, and at 120hz I don’t think that’s happening any time soon.
- drcross 6y agoSame. I'm at 7680x2160 pixels but over two 24 inch screens at 60hz. Once you get used to it you won't go back.
- JohnBooty 6y agoSame here. For coding work, I almost don't even see how it's worth discussing -- sheer real estate is going to win for me, every single time. I say "almost" because I've been doing this for nearly 25 years and I've learned that other coders have shockingly diverse preferences and styles. But still. Give me IPS, give me bucketloads of real estate. Everything else is secondary.
- deepspace 6y agoAgree, I use a 3840x2160 43" 16:9, which gives a 'low' density of around 100ppi, but I have absolutely no trouble reading the smallest text. There is no way that giving up the real estate would be worth an arbitrary increase in density.
- ptomato 6y agoYeah, I'm at 5120x1440 on a 49" ultrawide, and I'm not really interested in ever going back to a multi-monitor setup to get the same amount of real estate.
- Dylan16807 6y agoIt might be sooner than you think. 8K screens are easily available, 8K 120Hz screens have had working development versions for a while, and slightly cutting the height to 3200 means that you can fit the data into a single displayport 1.4 connection, using graphics cards that are already out.