If anyone wants to give an ELI5 or a link to a video that ELI5 I'd be incredibly thankful
I swear that all the stuff I find is like super in depth technical stuff that just loses me in no time flat
this post was submitted on 29 Apr 2024
476 points (96.5% liked)
linuxmemes
20880 readers
6 users here now
I use Arch btw
Sister communities:
- LemmyMemes: Memes
- LemmyShitpost: Anything and everything goes.
- RISA: Star Trek memes and shitposts
Community rules
- Follow the site-wide rules and code of conduct
- Be civil
- Post Linux-related content
- No recent reposts
Please report posts and comments that break these rules!
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
Basically, you should try it, if it works, keep using it; if it doesn't, switch to xorg to see if that fixes your problem.
Wayland is newer, have better support for multi-monitor, and application cannot see what you are typing in other app (so they cannot log your key and send your password to someone else).
It is the same on Windows, people can put a ahk script in your autostart, logs your password and send it to anyone on the internet, all without even invoking UAC.
So yeah, wayland is kind of important...
Is there a way to designate specific programs to be able to still have global access to your input? For instance specifically for AHK-type activities.
Yes, on wayland you will need to run a particular program as root to be able to read all keyboard input. See xremap or mouseless (unmaintained).
Since you already give the program plenty of trust to let it read all your inputs, I think running it as root is not outrages.
That being said, in an ideal scenario, we would be able to set fine-grained permissions like, allow to read keyboard input but deny communication with other app, networks, and storage etc. But I don't know any OS that can do this.
A more straightforward way to remap key is to get a keyboard with QMK firmware, that doesn't cover all the use case of ahk, xremap, or mouseless, but that don't require you to trust another program to run as root.
In my experience, it's way worse than Xorg. With Wayland, I cannot turn off my laptop screen but keep the external display, and having both monitors on at once can cause crashes when GPU acceleration is needed (videos or games). Somehow this is nVidia's fault, yet it works on Xorg with the same hardware.
If a driver doesn't behave properly, the things that are built on top of it won't work properly either. When that misbehaving driver is not open source, you're at the mercy of the vendor.. It's common knowledge for over a decade that nVidia drivers are problematic with Linux - especially on laptops. Bad drivers are entirely nVidia's fault.
I've been running Wayland with Intel graphics on my laptop and my desktop runs a Radeon. I've had 0 Wayland issues in the past years.
I use a laptop to run home console, and its display can turn off just fine.
I was intentionally vague in my response, since I don't want to confuse the reader. Specifically, the improvement I was referring to is when you run two monitor with different refresh rate or different scaling factor.