These just-so stories are easy to write, harder to write convincingly. I gladly use Wayland because I’m in a mixed-DPI setup, and didn’t rely on anything that broke. But loads of people are still pissed off due to persistent incompatibility.
The way Wayland made everything the responsibility of non-existent compositors really fucked over anyone not using GNOME or KDE, basically.
It’s fine. There’s still some quirks with Wayland I don’t like. Either having to be in a game or have Discord focused in order for push to talk to work for example. Some mouse constraint issues with certain games that for whatever reason KDE has been able to figure out but every other wayland compositor hasn’t.
Took a while, but Wayland is basically at a point now where it generally just works. I’m glad I don’t really need to deal with weird tearing issues or the X server not starting for whatever esoteric reason after a driver update anymore.
Wayland is a protocol, and major desktop versions like gnome and Kde implementation sucks balls…
Desktop crashes, oh there goes all my applikations that I started, gnome can’t keep up with switching workspaces because doesn’t fucking register the release key event. Fuck me dude xorg had no issues with switching windows or crashed barely crashed, gnome crashes 2 times a day. Oh sorry dude you want to use a custom screenshot tool, sorry dude, can’t allow that, have to do some weird workaround.
Oh you want change keybindings, no sorry dude can’t don’t support it.
Oh you wanted to automate window/workspace switching via scripts, you have inject fucking JavaScript into our runtime to query windows ids and state…
Jesus what joke of an implementation, it’s the anti theist of Linux. Everyone got fooled and allowed GUI developers implement the rendering backend…
And the best of all: hey do you want make software for Linux, sorry you app doesn’t work in KDE because the whole implementation of functionality you’re using is different from other Wayland implementation, can you plz fix in kde and gnome?
I have kde + Wayland on Arch, and everything works just fine even with my Nvidia card. About 1.5 years ago there was a
bugbig Wayland update that changed it from literally unusable to good but maybe a little buggy. Now it’s as stable as anything I’ve ever used.I use spectacle for screen shots without issue. Switch windows, desktops, snapping windows, etc works perfect for me. Other features you mentioned I can’t personally speak to, but not having all of the features on a rolling release is to be expected with anything. It’s early phases were bad though.
The event loop shit is a gnome issue I have, I haven’t tried it with KDE but I wouldn’t be surprised if the issue remains, where if you are switching windows/workspace to often the gnome event loop doesn’t register that you have released the key because it’s to busy fucking rendering the window/ Workspace switch.
We obviously don’t have the same use case, so if it works for you all power to you. But it sucks balls, the way I like use my laptop when I’m working. Can’t even do simple shit as to rebind a key, please find a working guide for kde or gnome, surprise they don’t work, and it’s fucking baffling the amount of different guides of how change keybindings and how many steps they require you do to, but they even work, why is that?
Why doesn’t Wayland support fucking a config file, where you define key bindings, why does it not allow to copy shit from the terminal via xclip or any other method, it’s like we went back 50 years in time, dude these tools existed 25 years ago.
Wtf is this, it’s lacking so much functionality and also performance is worse, you get more performance from xserver like 20% more fps, just try playing a game and turn on the fps meter, and compare them. Wtf is this, how do you build something new based on prior knowledge but it’s worse.
https://superuser.com/questions/1189467/how-to-copy-text-to-the-clipboard-when-using-wayland#1377550 In KDE, you can rebind the keybinds for anything, it’s under system settings in the keyboard section, I’m not really sure what you’re talking about. You can add custom ones to run any command, too, if the app doesn’t register a keybind, so you could, for example, send a dbus signal to the app. The way it’s done in wayland is different, but KDE supports all the stuff you mentioned in wayland from what I can tell.
I get very good fps in every game I play on my 2080ti that’s very much not new. I’ve had to download a fix for one game I have, and Sony doesn’t allow multiplayer in Ghost of Tsushima, but every other game literally loads and runs better than they ever have. 100fps+ in most games, and maybe less than 60 in the most intense. Arch + kde + Wayland is easily the best computing experience I’ve ever had.
I didn’t say Wayland had bad performance, if you read I said that x11 has better performance. For Wayland being new and more modern it should not underperform and dude just fucking look benchmarks online, you have internet.
Here this one is for free, how you candy read. https://www.dedoimedo.com/computers/wayland-vs-x11-performance-amd-graphics.html
I’ve had no performance degredation moving to Wayland after the aformentioned update. I read what you said. I’ve noticed no difference in performance, and anyone that’s fretting about 120 fps vs 110 fps is just splitting hairs for the sake of be being pedantic. I concede that there are some features that don’t exist that don’t apply to me and the vast majority of users, but for most of us, Wayland is just as good if not better in some common aspects.
No need to be hostile my dude. Chill.
Na I’ll always be hostile it’s more fun, I would less hostile if people stop the with telling what works for them, like I’m going to fucking get the same setup as dem. You do understand that there’s more angles than one, and not stopping and thinking yourself about the issue at hand and making weird assumptions without looking up anything, is kinda annoying after a while.
Because that is how most people are on Lemmy, it’s so hard to just have a discussion because you always have some people make counterpoints that fucking suck ass, and not based in anyone else’s reality but their own.
If I wouldn’t be hostile I would just stop writing, and it’s not like I’m angry, it’s just sounds funnier.
Well I don’t have GTX 2080ti, and I don’t like my computer sounding like wind turbine for playing a 7 year old game, so those performance benefits means something to me.
Gnome works great for me using Wayland.
Yeah sure, if you don’t anything with it
I use my PC for everything from digital art, music production, and video editing to 4k gaming without issue. I bet you have an nvidia GPU don’t you?
Yep, but my laptop I use the igpu
Unreasonably funny
I’m using gnome rn and it doesn’t crash much anymore. When I used xorg, there’d be crashes that brought down the entire desktop (or the computer as a whole) too. Also, generally every time I have a crash now it’s from using xwayland to play a game and having certain extensions enabled at the same time (although those issues seem to have disappeared recently too). All the other issues I either don’t care about or are supported with some extra work. For gnome, some of the issues are just because they have a phobia of exposing settings and you need to use stuff like dconf to deal with it.
Jesus what joke of an implementation, it’s the anti theist of Linux. Everyone got fooled and allowed GUI developers implement the rendering backend…
As you mentioned earlier, it’s a protocol. Implementation issues are due to how gnome/kde/whatever implemented their compositors. I think it’s pretty much standard for Linux given that stuff like systemd and flatpak exist. If you want to use something more traditional unix-y, maybe you should use a bsd or solaris derivative or something.
I still use x11 with suckless dwm, but for work I’m forced to use Ubuntu 25.10 gnome shit. It’s a sad state. Gnome owns all the process you start via gnome, that is why if gnome dies all the child process es dies as well, genius. Because the buggy mess, doesn’t critical errors and never will have…
I don’t know how you use gnome, if it doesn’t crash for you, fine, good. But that’s not my reality, it can crash because I open the laptop screen while being on an external monitor. It can crash because I’m screen sharing, it can crash because some software I used froze, it can crash for random reason (doesn’t happen often, but still annoying).
I still use x11 with suckless dwm
I can tell from the way you write, no need to mention it.
No worries, I would like you to have it in written statement.
kde crashes don’t exit your applications, kde crashes everytime my pc goes into sleep mode and it preserves the apps
The title of this article is a refreshing take on the Wayland vs X thing. I’ve had Wayland on my lunar lake PC and battery life nearly doubles with Wayland in-use. I can also have multiple monitor and resolution setups without issue at all. I had to use X unfortunately for a presentation I was recording and everything was just scaled terribly wrong.
I’ve had þe opposite experience. I have a laptop I ran X on for years. Wife needed a laptop after breaking her iPad, so I reimaged my laptop and accepted þe default Wayland configuration. Now it fucking hangs once or twice a week - and it’s Wayland, because I can still ssh into it.
I’m going to configure it to use X and uninstall Wayland.
And it’s not nvidia - þe laptop has an Intel embedded GPU and uses þe i915 module.
Worked perfectly fine under X for years; regularly hangs under Wayland.
Damn that 30 year old protocol for sneaking up on people.
I’ve discovered this once on my own, I had a complex control remapper and that I had been evolving into a horrific bash hydra of hacks over many years. I briefly tried to get it working when I switched to Wayland. I don’t remember which component broke me, but it went something like this:
“Hey, I wonder why doesn’t this thing work in Wayland. I wonder if I can whip up a pale imitation.”
10 minutes of stack overflow searches later…
“Oh… oh no.”“I tried to keylog myself and the system doesn’t support keylogging.” is a frustrating situation. Because it’s neat from a security perspective and absolutely maddening from basically every other one.
Not sure that’s a good thing.
It’s my own system and I’m root of it, if I want to run a program that inspects every bit of thing, including keylog myself I should be perfectly able to do it.
This kind of limitations are fake security, because Wayland is as secure as the rest of the stack it lies on top, it can’t add any more security than what Linux itself can guarantee. So yes, I can still read dev input and keylog myself anyway, it’s just more frustrating.
I have been using OSX since it was born because it was an amazing UNIX system and a convenient user environment. I moved back to Linux as my daily driven when they started introducing a tons of blockers to whatever I wanted to do “for security reasons”. “Oh you want to debug your own software?” “Nah, I can’t allow you to trace state of another process, I don’t care you are root” and so on…
People use windows because it has decades of backwards compatibility sort of.
That should be:
People
useused windows because ithashad decades of backwards compatibility sort of.Nowadays: it has current compatibility sort of.
Microsoft is a mess now, so it’s no surprise that their current Windows version is also a mess.
