Xorg is dead, long live Wayland - Red Hat Enterprise Linux (RHEL) dropping Xorg

Quoting: Adutchman

Quoting: slaapliedje

Quoting: tohur

Quoting: reaperx7I love how Red Hat loves to push (force) people to buggy and incomplete software touting it as "stable" when the truth is far from reality.

Wayland is nice, but the fact that every compositor does everything inconsistent with each other, and often conflicts with how Xorg/XWayland does things, with pretty much everything the original developers intend, pretty much leave me saying "this isn't a good idea".

Honestly, nothing was wrong with Xorg, in my opinion. It works as intended like Windows GDI+. Yes there were some security flaws, but really, what was wrong with Xorg? I honestly see Wayland as a solution in search of a problem, not the other way around. If there was consistency with the compositors this wouldn't be a problem, but Plasma has their own problems, Gnome wants to be the rebellious child, Enlightenment is their own thing, Weston is sitting in the corner rocking back and forth thinking its a tea pot, and God knows what else the rest are doing running around the house aimlessly, but nothing is consistent while Xorg is sitting at the table, well behaved and saying "Oh so I'm not that important anymore? Have fun with the miscreants!" as it sits it's tea and reads the newspaper.

If you think Xorg is well "behaved" and not an issue you do not live in reality.. xorg is a utter mess and needs to go. frankly since swapping to Plasma wayland my PC performs much better

In my mind, the only thing Xorg needed fixing on was a better / more supported way to not run as root. Outside of that, they did all the work to make it modular during the development from XFree86. The problem is that people don't like maintaining old stuff, and want to play with new toys. That's all Wayland is. It'll be a new toy, until it isn't, then someone else will declare that it's crap and no one should be using it and then we'll be in the exact same boat as before...

There are definitely things that Wayland does okay, but nothing they do that is special over X11, and end up still needing compatibility layer to X11...

Performance wise, I notice very little difference between Xorg / Wayland. Like somethings feel a little smoother, other things feel slower. I definitely notice things just not working right in Wayland though. Weirdly, I had an issue where the Synology Drive app didn't want to work in Xorg, but would in Wayland... after a reboot, it was fine though.

I think that isn't true. The reason we need something new is simple: Xorg was released in 2004. Pretty much everything is different now and with software, once it starts doing things that weren't concievable when it was designed, things start falling apart. "Modularity" isn't a checkbox, it is a relative thing. What a module was supposed to be was also thought up in 2004, so that is also inadequate. In 204, screens were 480p, screensharing did not exist, security was not really a designconsideration, VR was still science fiction and Linux desktop Linux was still very obscure. Stating that creating something new was just because people wanted something new is not really fair IMO.

Haha, in 2004? Monitors (which is why they were always more expensive than TVs) were definitely not 480p. I had a 1600x1200@85 monitor by then. Still have that same screen.

The whole point of it becoming modular was that they could update things as needed, without having to go through a ton of code to fix simple bugs. It was supposed to be to 'future proof' Xorg. It brought us such awesome things as the compositing that everyone is so fond of these days, so we could have wobbly windows, Compiz, etc. Screen sharing is possible in Xorg. Isn't that one of the things that is broken in Wayland? VR works... etc.

Only thing really is the security.

If anyone still asks "why Wayland instead of X", revisit this video:

https://www.youtube.com/watch?v=GWQh_DmDLKQ


Last edited by Shmerl on 7 December 2023 at 5:27 pm UTC

Quoting: slaapliedjeScreen sharing is possible in Xorg. Isn't that one of the things that is broken in Wayland?

Works fine in OBS for video capturing, so it's not broken. It needs mechanisms like portals or the like since it's a security related feature.

There is also this wip:

https://planet.kde.org/arjen-hiemstra-2023-08-08-remote-desktop-using-the-rdp-protocol-for-plasma-wayland/

Quoting: ShmerlPoint of Debian is a moot thing. A lot of people use Sid or testing for desktop purposes. You wouldn't want to use Debian stable for that purpose at all.

But, it's not a newbie friendly distro to use. I'd appreciate Debian testing becoming more officially desktop targeted distro (than Sid). But Debian developers never had enough resources or desire to do that.

My opinion on this is very skewed, as I find Debian extremely easy to set up and get going (and especially with the inclusion now of the firmware repo). Then again, I've been using it for so long, it's about as easy to install for me as breathing. Mind you, I'm comparing that to Utah weather, which very often is labeled as 'not safe for old people to be outside.'

Quoting: ShmerlIf anyone still asks "why Wayland instead of X", revisit this video:

https://www.youtube.com/watch?v=GWQh_DmDLKQ

Ha, I point out a few special use cases where Wayland doesn't work for me and some people (not you, you're sane) lose their shit.

There definitely are things that work better in it, like gestures seem to be better supported. I want to like Wayland, I like new things. It's just I keep running into very specific issues with it. One other thing that I don't think will ever be fixed is the ability to restart the Gnome Shell via Alt+F2 and R. Not sure of the technical reasons why, but I think it's because of how mutter is written?

One thing I do find amusing, if you run Debian Sid, and have an nvidia card, the Wayland sessions aren't available (at least without doing some shenanigans). It used to be easily added with just changing a line in the /etc/gdm3/gdm.conf. That hasn't seemed to work lately (though now I've switched to an AMD card in my main desktop).

About restarting the desktop shell, in KDE at least, It's Alt + F2 and then:

killall plasmashell; plasmashell

Not needed often, but doesn't feel complicated.


Last edited by Shmerl on 7 December 2023 at 6:04 pm UTC

Quoting: AdutchmanIn 204, screens were 480p, screensharing did not exist, security was not really a designconsideration, VR was still science fiction and Linux desktop Linux was still very obscure.

It's absolutely true that in 204, security wasn't really a design consideration -- and where did that leave us? Goths, Vandals, the Alamanni, and the Sassanids poured into the empire from all points of the compass. Wax tablets being limited to 480p was the least of our concerns back then.

Quoting: ShmerlAbout restarting the desktop shell, in KDE at least, It's Alt + F2 and then:

killall plasmashell; plasmashell

Not needed often, but doesn't feel complicated.

Yeah, I was just highlighting another little difference I found between an Xorg session vs a Wayland one.

Quoting: slaapliedjeWhy would you turn off Vsync, also, pretty sure Gnome got to Wayland support long before KDE. Which means they're wanting to drop Xorg support sooner. Also, Gnome is pretty much developed by Redhat at this point... so them wanting to drop Xorg support for RHEL 10 and Gnome wanting to do the same makes a whole lot of sense... if you think Wayland is ready (which I don't think it is).

The reason you turn Vsync off is input lag.. granted you don't notice it in most games but fast paced games you need Vsync off because in competitive games even moderate lag will get you killed. GNOME doesn't allow for you to turn it off in wayland and trust me in wayland you want Vsync off because with it on the lag is terrible.. for my preferred games GNOME is bad bad LMAO.. in KDE wayland there is a setting to allow screen tearing aka turnk off vsync for full screen apps aka games. the overall gaming experience is better on KDE


Last edited by tohur on 7 December 2023 at 11:21 pm UTC

Quoting: tohurThe reason you turn Vsync off is input lag.. granted you don't notice it in most games but fast paced games you need Vsync off because in competitive games even moderate lag will get you killed. GNOME doesn't allow for you to turn it off in wayland and trust me in wayland you want Vsync off because with it on the lag is terrible.. for my preferred games GNOME is bad bad LMAO.. in KDE wayland there is a setting to allow screen tearing aka turnk off vsync for full screen apps aka games. the overall gaming experience is better on KDE

I said it before, but whole turn vsync off for input lag idea is like couple decades or more old and is in practice outdated.

It originates from the time when everyone had 60 Hz displays. Those who worry about input lag today don't use such displays, so with adaptive sync and 144 Hz display (or even more) having tearing above monitor refresh rate range is of little value, because you won't notice much of a difference.

If you have 60 Hz monitor still - then yeah. So it's useful that KDE supports such scenario, but less useful than how it sounds.


Last edited by Shmerl on 7 December 2023 at 11:26 pm UTC

Quoting: Shmerl

Quoting: tohurThe reason you turn Vsync off is input lag.. granted you don't notice it in most games but fast paced games you need Vsync off because in competitive games even moderate lag will get you killed. GNOME doesn't allow for you to turn it off in wayland and trust me in wayland you want Vsync off because with it on the lag is terrible.. for my preferred games GNOME is bad bad LMAO.. in KDE wayland there is a setting to allow screen tearing aka turnk off vsync for full screen apps aka games. the overall gaming experience is better on KDE

I said it before, but whole turn vsync off for input lag idea is like couple decades or more old and is in practice outdated.

It originates from the time when everyone had 60 Hz displays. Those who worry about input lag today don't use such displays, so with adaptive sync and 144 Hz display (or even more) having tearing above monitor refresh rate range is of little value, because you won't notice much of a difference.

If you have 60 Hz monitor still - then yeah. So it's useful that KDE supports such scenario, but less useful than how it sounds.

bruh you clearly haven't compared GNOME vs KDE in this regard.. the Input lag in shooters and the such is bad enough it is noticeable lol. plenty of recent bug reports/ feature request out there to prove it is an issue now

Quoting: tohurbruh you clearly haven't compared GNOME vs KDE in this regard.. the Input lag in shooters and the such is bad enough it is noticeable lol. plenty of recent bug reports/ feature request out there to prove it is an issue now

I think Gnome's input lag has nothing to do with refresh rate, they just didn't optimize their own compositor for lower latency unlike KWin developers did. I.e. besides refresh rate delaying drawing, input lag can be caused by simply compositor doing any stuff before it's ready to draw. If you have too much of that - you'll have lag.

So yeah, Gnome might have such issue, but adding tearing won't help it if they don't optimize what they aren't doing efficiently, that's my point.


Last edited by Shmerl on 7 December 2023 at 11:41 pm UTC

Quoting: Shmerl

Quoting: tohurbruh you clearly haven't compared GNOME vs KDE in this regard.. the Input lag in shooters and the such is bad enough it is noticeable lol. plenty of recent bug reports/ feature request out there to prove it is an issue now

I think Gnome's input lag has nothing to do with refresh rate, they just didn't optimize their own compositor for lower latency unlike KWin developers did. I.e. besides refresh rate delaying drawing, input lag can be caused by simply compositor doing any stuff before it's ready to draw. If you have too much of that - you'll have lag.

So yeah, Gnome might have such issue, but adding tearing won't help it if they don't optimize what they aren't doing efficiently, that's my point.

input lag from vsync has squat to do with refresh rate honesly but is more noticable on certain refresh rates.. Vsync just naturally adds input lag regardless if you notice it or not. Honestly I feel like for me its only noticeable on high refresh rates as I play my games at 144hz


Last edited by tohur on 8 December 2023 at 12:35 am UTC

Quoting: tohurinput lag from vsync has squat to do with refresh rate honesly

It has a lot to do with that I'd say. If refresh rate is low (60 Hz) and compositor waits for vertial sync, you'll notice lag. Tearing means compositor doesn't wait and draws even if it will result in jagged image, so you'll see updates before the full refresh cycle even happens, which in practice means lower latency (lag). That kind of scenario benefits from enabling tearing.

Scenario when your refresh rate is 144 Hz and more reduces the period of blanks low enough that you don't notice anything even if compositor waits for it. But more importantly, you need to have adaptive sync (VRR) in order to avoid unnecessary waits. That's an improvement of the old style vsync.

There was a thread about it here: https://www.gamingonlinux.com/forum/topic/5185/

Here is a useful diagram:



I think using Vulkan mailbox present mode above the monitor refresh rate is similar to what AMD means by "enhanced sync".


Last edited by Shmerl on 8 December 2023 at 12:45 am UTC

Quoting: Shmerl

Quoting: tohurinput lag from vsync has squat to do with refresh rate honesly

It has a lot to do with that I'd say. If refresh rate is low (60 Hz) and compositor waits for vertial sync, you'll notice lag. Tearing means compositor doesn't wait and draws even if it will result in jagged image, so you'll see updates before the full refresh cycle even happens, which in practice means lower latency (lag). That kind of scenario benefits from enabling tearing.

Scenario when your refresh rate is 144 Hz and more reduces the period of blanks low enough that you don't notice anything even if compositor waits for it. But more importantly, you need to have adaptive sync (VRR) in order to avoid unnecessary waits. That's an improvement of the old style vsync.

There was a thread about it here: https://www.gamingonlinux.com/forum/topic/5185/

Here is a useful diagram:

To protect your privacy, external media requires approval to load. Source: i.imgur.com
View cookie preferences.
Accept & Show Accept All & Don't show this again   Direct Link

Which is why for me KDE trumps GNOME as Freesync works out the box on wayland. Last time I tried gnome don't think freesync worked thus the bad experience on top of using vsync

KDE supports it better, yeah. Except some scenarios where cursor breaks it, which I think is being addressed at Wayland protocol level before compositors will fix it. But Gnome just doesn't seem to focus on gaming use cases in general, so it takes them forever to add any adaptive sync support.


Last edited by Shmerl on 8 December 2023 at 12:53 am UTC

Quoting: tohur

Quoting: Shmerl

Quoting: tohurinput lag from vsync has squat to do with refresh rate honesly

It has a lot to do with that I'd say. If refresh rate is low (60 Hz) and compositor waits for vertial sync, you'll notice lag. Tearing means compositor doesn't wait and draws even if it will result in jagged image, so you'll see updates before the full refresh cycle even happens, which in practice means lower latency (lag). That kind of scenario benefits from enabling tearing.

Scenario when your refresh rate is 144 Hz and more reduces the period of blanks low enough that you don't notice anything even if compositor waits for it. But more importantly, you need to have adaptive sync (VRR) in order to avoid unnecessary waits. That's an improvement of the old style vsync.

There was a thread about it here: https://www.gamingonlinux.com/forum/topic/5185/

Here is a useful diagram:

To protect your privacy, external media requires approval to load. Source: i.imgur.com
View cookie preferences.
Accept & Show Accept All & Don't show this again   Direct Link

Which is why for me KDE trumps GNOME as Freesync works out the box on wayland. Last time I tried gnome don't think freesync worked thus the bad experience on top of using vsync

Input lag can be caused by a whole host of other things, outside of what software you're using even. There's a spreadsheet out there somewhere detailing all of the input lag of just using specific game pads versus another set of gamepads. I've never had any issues with input lag on gaming myself, though that could be because I'm too old to notice. But then if I don't notice, does it matter if it's there? It's like a fart you don't smell.

Amusingly, the main reason I flip between gnome/kde right now is because File-roller is broken as far as being able to drag / drop files into Nautilus at the moment (something about the transition to a new GTK or something is lagging behind). So when I am attempting to copy software over to a CF card for my DOS/Win9x machines, I flip to KDE. This is where I don't really notice any difference whether I'm using wayland or xorg, gnome or kde. I guess if I were bored stiff, I could run some benchmarks on some games to see if Wayland+KDE or Wayland+Gnome or Xorg+KDE or Xorg+Gnome can inch out a few more FPS here or there, or have less lag... but frankly don't give a crap. I've listed the reasons why Wayland 'doesn't quite work for me yet' and that I still need Xorg for over and over again.

I've said many times over, there should be a DE somewhere in between KDE and Gnome. Gnome seems to go for the simplistic, get out of your way desktop environment, and has some useful little quirks in it. KDE goes for the 'give you all the options you could ever think of, and 10x more that you couldn't, because someone else on the internet thought it up.' approach. Both approaches are valid, but I think there would be a lot to say about a DE that could hit right in the middle of that. Or even if KDE could figure out a 'simplified' way.

I used to prefer Gnome over KDE because GTK had cooler themes / and felt less like Windows. Now Gnome just reminds me of macOS, which I have learned to despise :P

Quoting: slaapliedje

Quoting: tohur

Quoting: Shmerl

Quoting: tohurinput lag from vsync has squat to do with refresh rate honesly

It has a lot to do with that I'd say. If refresh rate is low (60 Hz) and compositor waits for vertial sync, you'll notice lag. Tearing means compositor doesn't wait and draws even if it will result in jagged image, so you'll see updates before the full refresh cycle even happens, which in practice means lower latency (lag). That kind of scenario benefits from enabling tearing.

Scenario when your refresh rate is 144 Hz and more reduces the period of blanks low enough that you don't notice anything even if compositor waits for it. But more importantly, you need to have adaptive sync (VRR) in order to avoid unnecessary waits. That's an improvement of the old style vsync.

There was a thread about it here: https://www.gamingonlinux.com/forum/topic/5185/

Here is a useful diagram:

To protect your privacy, external media requires approval to load. Source: i.imgur.com
View cookie preferences.
Accept & Show Accept All & Don't show this again   Direct Link

Which is why for me KDE trumps GNOME as Freesync works out the box on wayland. Last time I tried gnome don't think freesync worked thus the bad experience on top of using vsync

Input lag can be caused by a whole host of other things, outside of what software you're using even. There's a spreadsheet out there somewhere detailing all of the input lag of just using specific game pads versus another set of gamepads. I've never had any issues with input lag on gaming myself, though that could be because I'm too old to notice. But then if I don't notice, does it matter if it's there? It's like a fart you don't smell.

Amusingly, the main reason I flip between gnome/kde right now is because File-roller is broken as far as being able to drag / drop files into Nautilus at the moment (something about the transition to a new GTK or something is lagging behind). So when I am attempting to copy software over to a CF card for my DOS/Win9x machines, I flip to KDE. This is where I don't really notice any difference whether I'm using wayland or xorg, gnome or kde. I guess if I were bored stiff, I could run some benchmarks on some games to see if Wayland+KDE or Wayland+Gnome or Xorg+KDE or Xorg+Gnome can inch out a few more FPS here or there, or have less lag... but frankly don't give a crap. I've listed the reasons why Wayland 'doesn't quite work for me yet' and that I still need Xorg for over and over again.

I've said many times over, there should be a DE somewhere in between KDE and Gnome. Gnome seems to go for the simplistic, get out of your way desktop environment, and has some useful little quirks in it. KDE goes for the 'give you all the options you could ever think of, and 10x more that you couldn't, because someone else on the internet thought it up.' approach. Both approaches are valid, but I think there would be a lot to say about a DE that could hit right in the middle of that. Or even if KDE could figure out a 'simplified' way.

I used to prefer Gnome over KDE because GTK had cooler themes / and felt less like Windows. Now Gnome just reminds me of macOS, which I have learned to despise :P

Yes thats true input lag can because by many things but in my case I think its a mixture of being locked to using Vsync and not having proper Freesync support in GNOME on wayland and the games I tend to play I notice the lag thus why KDE is just better in this regard. Honestly haven't liked GNOME since they have started down the path of mimicking Apple/macOS in every way possible.. the good, bad and the ugly.

Also KDE does have it in the plans to make a simplified settings app and just app settings in general for folks that just want the out the box experience and basic customization.. and have the rest the settings toggled on with a advanced toggle or something... Theres an Youtuber thats a KDE dev that talked about it some months back on one of his videos


Last edited by tohur on 8 December 2023 at 4:21 am UTC

Quoting: tohur

Quoting: slaapliedje

Quoting: tohur

Quoting: Shmerl

Quoting: tohurinput lag from vsync has squat to do with refresh rate honesly

It has a lot to do with that I'd say. If refresh rate is low (60 Hz) and compositor waits for vertial sync, you'll notice lag. Tearing means compositor doesn't wait and draws even if it will result in jagged image, so you'll see updates before the full refresh cycle even happens, which in practice means lower latency (lag). That kind of scenario benefits from enabling tearing.

Scenario when your refresh rate is 144 Hz and more reduces the period of blanks low enough that you don't notice anything even if compositor waits for it. But more importantly, you need to have adaptive sync (VRR) in order to avoid unnecessary waits. That's an improvement of the old style vsync.

There was a thread about it here: https://www.gamingonlinux.com/forum/topic/5185/

Here is a useful diagram:

To protect your privacy, external media requires approval to load. Source: i.imgur.com
View cookie preferences.
Accept & Show Accept All & Don't show this again   Direct Link

Which is why for me KDE trumps GNOME as Freesync works out the box on wayland. Last time I tried gnome don't think freesync worked thus the bad experience on top of using vsync

Input lag can be caused by a whole host of other things, outside of what software you're using even. There's a spreadsheet out there somewhere detailing all of the input lag of just using specific game pads versus another set of gamepads. I've never had any issues with input lag on gaming myself, though that could be because I'm too old to notice. But then if I don't notice, does it matter if it's there? It's like a fart you don't smell.

Amusingly, the main reason I flip between gnome/kde right now is because File-roller is broken as far as being able to drag / drop files into Nautilus at the moment (something about the transition to a new GTK or something is lagging behind). So when I am attempting to copy software over to a CF card for my DOS/Win9x machines, I flip to KDE. This is where I don't really notice any difference whether I'm using wayland or xorg, gnome or kde. I guess if I were bored stiff, I could run some benchmarks on some games to see if Wayland+KDE or Wayland+Gnome or Xorg+KDE or Xorg+Gnome can inch out a few more FPS here or there, or have less lag... but frankly don't give a crap. I've listed the reasons why Wayland 'doesn't quite work for me yet' and that I still need Xorg for over and over again.

I've said many times over, there should be a DE somewhere in between KDE and Gnome. Gnome seems to go for the simplistic, get out of your way desktop environment, and has some useful little quirks in it. KDE goes for the 'give you all the options you could ever think of, and 10x more that you couldn't, because someone else on the internet thought it up.' approach. Both approaches are valid, but I think there would be a lot to say about a DE that could hit right in the middle of that. Or even if KDE could figure out a 'simplified' way.

I used to prefer Gnome over KDE because GTK had cooler themes / and felt less like Windows. Now Gnome just reminds me of macOS, which I have learned to despise :P

Yes thats true input lag can because by many things but in my case I think its a mixture of being locked to using Vsync and not having proper Freesync support in GNOME on wayland and the games I tend to play I notice the lag thus why KDE is just better in this regard. Honestly haven't liked GNOME since they have started down the path of mimicking Apple/macOS in every way possible.. the good, bad and the ugly.

Also KDE does have it in the plans to make a simplified settings app and just app settings in general for folks that just want the out the box experience and basic customization.. and have the rest the settings toggled on with a advanced toggle or something... Theres an Youtuber thats a KDE dev that talked about it some months back on one of his videos

There apparently are ways to enable Freesync within Xorg... I know G-Sync worked when I had nvidia. All three of my monitors support GSync but according to xrandr, only one of them supports Freesync. Wayland requires the DE apparently to enable it?

Quoting: slaapliedje

Quoting: tohur

Quoting: slaapliedje

Quoting: tohur

Quoting: Shmerl

Quoting: tohurinput lag from vsync has squat to do with refresh rate honesly

It has a lot to do with that I'd say. If refresh rate is low (60 Hz) and compositor waits for vertial sync, you'll notice lag. Tearing means compositor doesn't wait and draws even if it will result in jagged image, so you'll see updates before the full refresh cycle even happens, which in practice means lower latency (lag). That kind of scenario benefits from enabling tearing.

Scenario when your refresh rate is 144 Hz and more reduces the period of blanks low enough that you don't notice anything even if compositor waits for it. But more importantly, you need to have adaptive sync (VRR) in order to avoid unnecessary waits. That's an improvement of the old style vsync.

There was a thread about it here: https://www.gamingonlinux.com/forum/topic/5185/

Here is a useful diagram:

To protect your privacy, external media requires approval to load. Source: i.imgur.com
View cookie preferences.
Accept & Show Accept All & Don't show this again   Direct Link

Which is why for me KDE trumps GNOME as Freesync works out the box on wayland. Last time I tried gnome don't think freesync worked thus the bad experience on top of using vsync

Input lag can be caused by a whole host of other things, outside of what software you're using even. There's a spreadsheet out there somewhere detailing all of the input lag of just using specific game pads versus another set of gamepads. I've never had any issues with input lag on gaming myself, though that could be because I'm too old to notice. But then if I don't notice, does it matter if it's there? It's like a fart you don't smell.

Amusingly, the main reason I flip between gnome/kde right now is because File-roller is broken as far as being able to drag / drop files into Nautilus at the moment (something about the transition to a new GTK or something is lagging behind). So when I am attempting to copy software over to a CF card for my DOS/Win9x machines, I flip to KDE. This is where I don't really notice any difference whether I'm using wayland or xorg, gnome or kde. I guess if I were bored stiff, I could run some benchmarks on some games to see if Wayland+KDE or Wayland+Gnome or Xorg+KDE or Xorg+Gnome can inch out a few more FPS here or there, or have less lag... but frankly don't give a crap. I've listed the reasons why Wayland 'doesn't quite work for me yet' and that I still need Xorg for over and over again.

I've said many times over, there should be a DE somewhere in between KDE and Gnome. Gnome seems to go for the simplistic, get out of your way desktop environment, and has some useful little quirks in it. KDE goes for the 'give you all the options you could ever think of, and 10x more that you couldn't, because someone else on the internet thought it up.' approach. Both approaches are valid, but I think there would be a lot to say about a DE that could hit right in the middle of that. Or even if KDE could figure out a 'simplified' way.

I used to prefer Gnome over KDE because GTK had cooler themes / and felt less like Windows. Now Gnome just reminds me of macOS, which I have learned to despise :P

Yes thats true input lag can because by many things but in my case I think its a mixture of being locked to using Vsync and not having proper Freesync support in GNOME on wayland and the games I tend to play I notice the lag thus why KDE is just better in this regard. Honestly haven't liked GNOME since they have started down the path of mimicking Apple/macOS in every way possible.. the good, bad and the ugly.

Also KDE does have it in the plans to make a simplified settings app and just app settings in general for folks that just want the out the box experience and basic customization.. and have the rest the settings toggled on with a advanced toggle or something... Theres an Youtuber thats a KDE dev that talked about it some months back on one of his videos

There apparently are ways to enable Freesync within Xorg... I know G-Sync worked when I had nvidia. All three of my monitors support GSync but according to xrandr, only one of them supports Freesync. Wayland requires the DE apparently to enable it?

The wayland compositor for the DE needs to support it.. thus for GNOME they need to add it to mutter I think. KDE added it to kwin_wayland ages ago. as far as wayland goes KDE is quite ahead of GNOME as they will be adding HDR in plasma 6 on wayland.. I tried to enable freesync on xorg before I completely swapped to wayland but could never get it to work properly.. on plasma wayland was a simple setting on the display configuration in the settings app


Last edited by tohur on 8 December 2023 at 5:09 pm UTC