upvote
Doesn't it work perfectly with a 2880px-wide display with 2x scaling?
reply
It just, just not enough real estate!
reply
As a heavy fractional scaling user, as long as the display has enough DPI, it's a non-issue. At my last job I was happily running 1.35 scaling, and I run my TV at 1.5 scaling. Make sure you're using a sane compositor, which excludes DWM; most Wayland compositors should run just fine.
reply
Glad it works for you. It runs fine, but details become blurry as they get spread across pixels,

I do UI design, so I find it important to see things in full fidelity (no pixel smudging).

reply
Well I'd argue it'd help you to make designs that don't require perfect pixel alignments to look good, the same way developers should run crappy 10 year old computers. But that's the sadistic way. Anything graphics-related does require 1:1 display.

However, to be fair, that's only at lower DPIs smudging's an issue. Anything retina-ish and integer scaling loses all meaning. I'm typing this on a 15" 4K laptop on 1.75 scaling with HN set to 120% zoom. At those DPIs, it does not matter at all. I adjust most websites zoom level because a lot of them think the content must breathe, while I think I should not fiddle with my scroll to read a paragraph.

reply
Forget fractional scaling, just keep scale at 100% and increase font and icon sizes.
reply
Which is something like 2/3rds successful in my experience (I use this daily), and requires tons of fiddling to get things looking even mostly reasonable (lots of misalignments and funky padding otherwise). And lots of applications don't respect it and you're stuck with too-small controls when it fails. Which makes it a noticeably-worse success rate than fractional scaling, afaict.

I still use it because the end result on some of my most-used applications is nicer, and it seems to be slightly-noticeably better performing (on a high framerate screen). So it's good enough for my tastes. But it really isn't anything I'd call "successful".

reply
on omarchy ill switch with super + / and use 1x, 1.6x and 2x when needed.

1.6x works surprisingly well now, that wasnt the case a couple years ago

reply