346
KDE Going all-in on a Wayland future
(blogs.kde.org)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 26 Nov 2025
346 points (100.0% liked)
Linux
60027 readers
174 users here now
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
founded 6 years ago
MODERATORS
that's mainly because of Wayland's security model I think, it's trading a tiny bit of convenience for lots more security in terms of things like preventing easy keylogging.
You can still do keylogging in wayland but that has to be done at the compositor or evdev layer, which requires root access or control of the DE, which makes it more secure. I'm sure you could write something in C to do this though
It might be an annoyance for you and I get that, but your small annoyance improves security for lots more people than you realise. I'm sure you can adapt to not using the script though (I also use multiple layouts and I work fine without a script like this)
I get what you are saying and understand the balance between convenience and security, however most end users don't care. Their thing stops working and they complain "Wayland bad, my workflow now broken!", nothing you can do.
Right, but the point is that for most end users, their workflow isn't broken.