this post was submitted on 19 Mar 2024
105 points (60.6% liked)
linuxmemes
21387 readers
1307 users here now
Hint: :q!
Sister communities:
Community rules (click to expand)
1. Follow the site-wide rules
- Instance-wide TOS: https://legal.lemmy.world/tos/
- Lemmy code of conduct: https://join-lemmy.org/docs/code_of_conduct.html
2. Be civil
- Understand the difference between a joke and an insult.
- Do not harrass or attack members of the community for any reason.
- Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
- Bigotry will not be tolerated.
- These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
3. Post Linux-related content
- Including Unix and BSD.
- Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of
sudo
in Windows. - No porn. Even if you watch it on a Linux machine.
4. No recent reposts
- Everybody uses Arch btw, can't quit Vim, and wants to interject for a moment. You can stop now.
Please report posts and comments that break these rules!
Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't fork-bomb your computer.
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Nothing to do with the hardware. It's the lack of fractional scaling support and not knowing the workarounds
200% isn't fractional scaling, though
It has everything to do with the hardware. This specific piece of hardware is not as compatible as a regular DPI display.
These problems only exist because of this poor hardware choice on Framework's part.
If they go from the resolution they used to native 4k, they waste a lot of battery life. If they go the other way, you have low res. I think they happened to pick within a golden DPI range. Not too high or low.
On KDE Wayland, I really don't really see any blurriness issues. I'm not even on KDE 6 yet.
The irony is that my old "low res" laptop looks sharp and crisp while "high res" looks blurry. My old laptop doesn't require me to give up my distro of choice (Arch btw), doesn't require me to give up apps I like, and doesn't require me to spend days applying workarounds that ultimately don't even completely solve the problem.
why would high dpi rule out arch??
BECAUSE THERE'S NO EXE!!!
..?
I use Arch on a Framework 13 and 125% scaling in KDE. It works fine and I honestly forget that it's not at 100% scale. The only big issue I've seen is when you have multiple monitors with different scaling, some applications can get a bit confused, especially if the edge of the window is touching the edge between two monitors with different scaling.
SIMP'ing to the max here. Sorry not sorry .
Just get Windows if you can't manage the pitfalls of Linux