Why is <220 ppi a dealbreaker? 27 inch 4k displays seem fine to me for retina and they are quite abundant. Though I've tried 32 inches 4k, and there the resolution is not enough for text work.
Dell has a 32 inch 8k display which is ~280 ppi in stock.
If you're on macOS, your choice for a 27" 4K is realistically either the 'looks like 1080p' high DPI mode, or the 'looks like 1440p' high DPI mode. The 'looks like 1080p' mode makes all of the UI elements huge. The 'looks like 1440p' mode makes text slightly fuzzy as it's being downscaled from 5120x2880 to 3840x2160.
It's not terrible, but it's nowhere near as nice as the 27" 5K.
This specific issue is definitely a macOS problem - instead of doing proper resolution independent rendering, macOS just renders at 2x the 'looks like' resolution, and then scales the result to fit the panel.
But even on Windows, the choices at 27" 4K aren't great. 100% is too small. 200% is too large. 150% is quite nice, but I find apps regularly don't scale properly, and text still isn't as nice as 200% on a 5K display.
edit: and on Linux, it's similarly not great - integer scaling works quite well on most modern DEs. Fractional scaling is a mixed bag and a lot of apps have broken or compromised UI when it's in use.
I use a triple monitor setup with the LG 24UD58-B. 24", 4K, $300. 2X scaling is absolutely perfect on it. 27" is not a good monitor size for this, I agree.
As an aside, a user here recommended putting the outside monitors in vertical mode with the middle monitor in horizontal mode. It works extremely well for reading websites/documentation/terminal output while coding in the middle panel.
It's cheap enough that I've been tempted to pick up one of these to try, but I think going back to 24" would be a little frustrating for side-by-side editing in an IDE.
> Fractional scaling is a mixed bag and a lot of apps have broken or compromised UI when it's in use.
I use 1.5× scaling in Sway, and haven’t observed even the slightest problem in any Wayland app. (I also use the high-DPI patches for XWayland, and run it at 3×, so that it’s an integer multiple of my scaling factor, a minor visual improvement on the very few X11 things I use that is probably not worth it.) I will note, however, that Firefox is rendering content at 2× and downscaling; setting the experimental widget.wayland.fractional_buffer_scale to 1.5 distinctly improves rendering, but had some very annoying bugs when I tried it several months ago which became debilitating maybe a couple of months ago, so I gave up on it.
The one that sticks in my memory the most was a bunch of issues with Qt-based apps in particular where UI would scale in 1x, 2x, 3x steps, but font size would scale with the fractional size specified.
I have a few Qt apps and haven’t observed anything like this; most likely that’s been fixed. I’ve been using Wayland since April.
(One thing that is comically broken about Sway and I think Wayland in general is cursor sizes. Specifying `seat seat0 xcursor_theme Adwaita 96` nets me at least four or I think five different cursor sizes, varying by app, and at least one of the dodgy sizes is actually a fractional scaling bug, scaling by ceil(1.5) rather than 1.5.)
Ummm, I think 274K on 200% is definitely fine? I just use it as 1080p with better text rendering and graphic. I don't even use it at 150% because that at a 50 ~ 60 viewing distance isn't really a pleasure experience. Did you place the monitor very close to your eyes?
I'm using a 28" 4K (with Wayland, which does scaling exactly like macOS) — used to use 1.5x with downscaling but switched to 2x "huge UI" for perfect crispness and honestly? It's not bad. It's actually good. Don't fear the big buttons :)
> switched to 2x "huge UI" for perfect crispness and honestly? It's not bad. It's actually good. Don't fear the big buttons :)
There's always a balance and trade-off here.
2x scaling with 4k really means you end up with the same screen real estate as 1080p.
In my opinion I would very much prefer 24" or 25" at 1440p with native scaling which is ~120 PPI. I personally run both a 25" 1440p display and another 24" 1440p display at 1x. I still consider going from 1080p to 1440p one of the biggest quality of life upgrades I've encountered when I made the switch 7 years ago. It's the same level of "wow this is great" as going from a HDD to SSD.
Before there were shortages you could get a high quality IPS panel monitor from a reputable brand (Dell, ViewSonic) with low input latency for around $300. 4k at 1.5x also gives you the same real estate as 1440p but with higher PPI but I don't know how crisp that will be given the scaling ratio.
>2x scaling with 4k really means you end up with the same screen real estate as 1080p.
Yes and no. With much clearer looking text, I can use smaller fonts (13 -> 11 in IntelliJ) than on regular 1080p displays, so there's _some_ difference.
For reference I'm at 25" 1440p with a font size of 9 using Consolas. Things look pretty crisp at native scaling and also very comfortable to read with no strain.
In terms of viewing space this fits (4) side by side code windows at 80 characters with a little bit of breathing room.
Yep, 27" 4k at 1.5x (plasma) I can have 50/50 or 60/40 with font size 14 and get 110+ characters, not just 80. 60/40 would be for an IDE with a bar or two on the side and still get almost 110 columns in the editor/console comfortably without eye strain. With 144 DPI fonts on plasma (using Hack), fonts seem plenty crisp to me down to size 5.
For screen size, I think there is some screen size that's most comfortable to view, and I want to say that's like ~40% of the human FOV... so, I think a 24" monitor and 15" laptop are most comfortable for me, but 27" might be a bit nicer if you're using it for media as well.
I miss read a bit when replying in the other comment, for 4 side-by-side 80 column windows, you'd need to bring the font size to 9, which isn't as comfortable as 14 for me in my side-by-side setup, but then 1.25x is also an option.
> you end up with the same screen real estate as 1080p.
Is that even a problem? I am not buying better screen to torture my eyes. IMO. A smaller sharper text won't really be easier to see compared to a larger but blurrer text.
I wear glasses and 25" at 1440p has very clear text. I feel no strain. Even the grey text on HN is very readable from about 32" (81 cm) away which is my normal viewing distance. It's readable without much strain from 45" (114 cm) but I wouldn't want to use things that far away.
For reference my work issued laptop is a 13" 2020 MBP so I have experienced retina. I would take the 1440p screen real estate at ~120 PPI (24"/25") 10 out of 10 times vs going back to 1080p but with higher PPI. There's also the added benefit of never having to think or worry about poor UI scaling since not all apps handle scaling well, but that's not a deciding factor in my mind, more of a nice to have.
I never need to run app and editor side by side on same screen. I always have 2+ screen in any setup. So I just threw it to another if I want ever want to run it side by side. And besides, I seldom codes with my 27 4K screens.
They ares used mostly on browsing web/gaming. which you can't use something side by side isn't even a issue.
Yes, for developers screen real estate is everything. You want crisp fonts and lots of space. Both for just code editing and of course for testing, where you often run your application side by side with your code window. At work I still use my old 30" 2560x1600 screen (basically the old cinema display) and its just gorgeous. My iMac is way sharper, that is also great for image processing, but already noticeable smaller. You can squeeze a bit more onto the screen due to the higher resolution. My 24" 4k screen works with a scaled resolution (2300 horizontal resolution) but its considerably worse. A hidpi 30" screen would be a dream.
No, Sway supports downscaling. Augmenting downscaling with exact fractional scales is still in discussion: https://gitlab.freedesktop.org/wayland/wayland-protocols/-/i... (And Firefox has a prototype implementation using wp_viewporter but you have to set the scale manually.)
Of course, independent of the desktop environment, you could just tell supporting applications to just manually render bigger UI (exactly how you would on X11 with some TOOLKIT_DPI variable thing per UI toolkit) and keep the monitor scale in the compositor at 1x. That's probably what you've been doing. That doesn't support multiple monitors with varying scale.
I have been using Dell P2415Q (24" 180ppi) for a few years side-by-side with a Retina MacBook, and the difference is visible: I can see pixels on 180ppi text if I lean forward, but not on the 220ppi. Not a deal breaker, of course, but the "retina" marketing pitch isn't lying.
BTW, LG 24UD58 mentioned in the article is also only 180ppi.
I am using the same, as I needed an external screen for my MacBook. I use it in scaled resolution for screen estate (2300 horizontal pixels), which works, but isn't as sharp as my iMac.
> Why is <220 ppi a dealbreaker? 27 inch 4k displays seem fine to me for retina and they are quite abundant.
I regret buying a 27 inch 4K monitor each and every day.
Sure, the PPI is much better than my 24 inch 1200p Dell Ultrasharp but a 27 inch 4K needs wither fractional scaling, which is a mess, or scaling fonts, which makes UI elements look weird.
24 inch 4K and 27 inch 5K should be a standard but all monitor OEMs are interested in making shitty gaming monitors.
Dell has a 32 inch 8k display which is ~280 ppi in stock.
https://www.dell.com/en-us/work/shop/dell-ultrasharp-32-8k-m...