I'd do anything for 5K, 120Hz, Mini-LED or Micro-LED displays with 10-bit color and HDR. I don't want 4K: 5K has over 77% more logical area.
They don't have to be cheap. I'll pay well. I just want them to exist. I've been waiting over a decade at this point!
but with a 4K screen, you have three options: 1. no scaling and tiny fonts (ugh), 2. fractional scaling (ugh), or 3. 2x scaling and settle for 1080p real estate (ugh)
IMO 5K > 1440p > 4K > 1080p
Have you ever switched from a high refresh rate screens to a 60 Hz screen and noticed a difference? I find this to be similar.
The products basically don't exist.
I can get some rather fantastic 1440p displays -- HDR, 165Hz, DCI-P3 color gamut, and excellent color reproduction (especially when calibrated) for as cheap as $260 on sale. Best thing imaginable? No, but amazing for the price, and objectively better in every measure than the 1440p displays that were $1000+ in 2010.
I'd pay $2000 -- perhaps even $2500 -- each (and I'd buy THREE), for a 5K display that met my requirements.
-- -----
Hardware Unboxed recently made a video complaining that the display market is too heavily driven by gamers wanting a specific, narrow feature set for a rock bottom price.
Display makers have delivered that. However they don't really make much of anything else as a result.
It's a nasty, difficult, low-margin business where almost no one is making money, hence why it's huge volumes of largely the same thing with no major shifts forward.
The bigger issue than low margins is the "4k" marketing and lack of large buyers other than Apple for 5k displays. I think early on in the 4k hype train, there was a bandwidth issue with Display port that required MST for 5k.
Unfortunately 200+PPI are extremely expensive. So 5K panel at 27"+ are partially speaking an Apple only SKUs.
Can you elaborate?
5/4 = 1.25
Since they are both the same aspect ratio (16:9) you can also take the ratio of one linear dimension and square it to get the area ratio.
So:
(5120/3840)^2 = (2880/2160)^2 = 1.777
4k is 4096 x 2160, 5k is 5120 x 2880
There's also a really helpful diagram on that page
(5120 × 2880) / (4096 × 2160) = 1.6666
The way I'm running 4k 27" on Mac is setting scaling to 2x ("looks like 1080p) - which gives the crispest UI, and set scaling appropriately in a small set of applications so that they are not too huge. Just running the browser at 90% default scaling makes things pretty decent. And then maybe reducing the font size by 1pt on one or two text editors.
Wayland does not have those issues and is very nice in my experience although I hear that screen sharing is still a work in progress.
I mean apps that talk directly to the Wayland protocol without XWayland in between, which includes Firefox, Chrome, graphical Emacs, all the Gnome apps.
Even if Wayland were to support fractional scaling: Gtk doesn't support fractional scaling at the toolkit level - integer scaling only [2]. Although it's worth noting Qt and Electron could probably support fractional scaling today. The general philosophy being pushed on the Linux desktop is to do scaling like macOS, but unfortunately it combined that bad philosophy with a worse implementation.
Wayland is a blessing for the Linux desktop, but sadly the free desktop is still waiting to be dragged into the 21st century in many respects.
[1]: https://www.reddit.com/r/kde/comments/lficfe/wayland_fractio...
[2]: https://gitlab.freedesktop.org/wayland/wayland-protocols/-/i...
Your reference [2] is on the topic of Wayland, not GTK. Although the referenced page does contains 2 occurences of "GTK", after reading the context of those occurences, I am unable to find or infer anything in support of your assertion that GTK doesn't support fractional scaling.
Also, your reference [2] implies that there are two scaling factors. Specifically at the top of your ref [2] is a link to another page (issue #34), in which a participant, "Pekka Paalanen, Maintainer", writes,
>Fractional scaling is a whole another topic apart from UI scale. I want to mention it to avoid confusing the two. . . . This is different from UI scale, because it is effectively a fractional buffer scale, without changing the UI size.
The title of your ref [2] is "Add support for fractional scaling", which was written 9 months ago, at which time I was already using fractional scaling (what I mean by fractional scaling and the meaning that is relevant in the current thread of conversation) in released software (namely Gnome 40 on Fedora 34) -- which is another sign that you've incorporated information that is correct in one specific context, but you've erroneously applied it to a different context.
Skipping forward in your ref [2] by 3 sentences, we read, "The current Wayland protocol allows clients to scale their buffers by an integer scale factor" (emphasis mine).
But most of the elements -- particularly 99.9% of the text -- on a modern operating system are stored on the computer as mathematical descriptions of curves. The big exceptions to this are JPEG and PNG files (hence the interest in SVG). (Another exception is "bitmap" fonts, but IIUC the only people looking at bitmap fonts these years are techies who have specially configured their OS or their apps to use bitmap fonts.) These mathetical descriptions have no native resolution: they can be rendered cleanly at any scaling factor.
I use Gnome Settings to tell my computer how large I want things to be, then the text is rendered at that particular scaling factor. There is never any moment in which any framebuffer or rectangular region intended to be displayed on the screen is scaled (again excepting JPGs and PNGs). I know this because I have not been using a HiDPI monitor, so I can see the individual pixels in my monitor. There is no way for the text on my computer to look as good as it does if it were being rendered into a buffer, followed by that buffer's being scaled. I would be able to tell the difference. Unless you want to try to tell me that changing the text size in Terminal.app on a Mac to some size other than the default size causes text to be rendered into a buffer, then the buffer gets scaled before being shown to the user. Or when in Google Chrome, I use the "hamburger menu" to set the "Zoom" of a web site to something other than 100%, that web page is being rendered, then scaled.
Note that Google Chrome and Firefox do their own text rendering: they do not rely on the host OS to do it like most apps do. Consequently, exploring the Zoom setting in Chrome is a good way to experience what scaling on a pure-GTK3 Linux install is like, only that the scaling factor on Linux applies to everything on the screen (including the mouse cursor) whereas in Chrome it only applies to the viewport (minus the mouse cursor).
Again, IMO the people in your reference [2] are talking about a technical detail different from the detail you think they are. Maybe that detail is relevant when you have 2 monitors of different native resolutions and you drag a window from one monitor to another. But that is not the topic of conversation here. Here we are talking about users with a single monitor who because they didn't do enough research before buying the monitor, are faced with a choice of the text's being too big or too small. That can happen on MacOS, but will never happened on a pure-GTK3 Linux install. Pick whatever native resolution, monitor size or pixel density you want: the Linux install can be adjusted so that things are not too big and not too small. (And it takes only 2 seconds to switch sizes: any windows that are open when you switch automatically adapt.) Specifically, on a monitor with 1680 horizontal pixels, Gnome Settings is giving me the following choices for the scaling factor: 100%, 125%, 150%, 175%, 200%. My guess is that if my monitor had more horizontal pixels, I would get more choices.
System Preferences on a Mac (specifically the Display ("Displays"?) pane) also gives you some choices that make everything bigger or smaller, but if you don't choose the native resolution of the display, everything is very blurry -- which does not happen on a pure-GTK3 Linux install.
ADDED. you have to run the following command (once per install) to activate the "Scale" line in the Display pane of Gnome Settings:
gsettings set org.gnome.mutter experimental-features "['scale-monitor-framebuffer']"> System Preferences on a Mac (specifically the Display ("Displays"?) pane) also gives you some choices that make everything bigger or smaller, but if you don't choose the native resolution of the display, everything is very blurry -- which does not happen on a pure-GTK3 Linux install.
It absolutely does. You may not see it, but Wayland and Gtk as of 2022 are not able to do technically anything else here than scaling. This is a known issue, and the reason why I linked that Wayland fractional scaling thing - it is not possible on regular desktop Linux (it is on Android/ChromeOS) to get adequately sized, rendered for size output on your 27" 4K screen or 13" 1080p screen.
https://bjango.com/articles/macexternaldisplays/
TLDR: use monitors that are around 110 or 220 PPI. The 27" 4K is right in the middle at 163 PPI.
I'd gladly take a monitor like this at 2× the resolution of course (so 5K), but again, if I could choose, not at 27" but at 30".
At least when i upscale older (or very demanding) games from 640x480 or 1280x720 they look crisp enough instead of the blurry mess that was before a few years when this became possible outside of emulation.
But i bought it because of the VA panel, 165Hz refresh rate and flat surface since i couldn't find any smaller monitor with those characteristics. So if that next-best-thing-to-OLED tech is actually good, i'll most likely get one since i doubt i'll see a real OLED PC monitor in not-gargantuan sizes.