Comment by thisislife2

Comment by thisislife2 5 days ago

Yeah, I am staunch proponent of "don't try to fix what is not broken". Current XFCE is fast, light-weight, usable and works fine without major issues. While I don't fully understand the advantages / disadvantages of XFCE using Wayland instead of X, if, as someone else pointed out here on HN, running XFCE on Wayland is going to make it slower, it means these developers will be crippling one of XFCE's strongest feature. In that case other minor advantages seems pointless to users like me.

happymellon 5 days ago

> running XFCE on Wayland is going to make it slower

Citation. None of the other desktops have slowed with Wayland, and gaming is as fast as, if not marginally faster on KDE/Gnome with Wayland vs LXDE on X.

https://www.phoronix.com/review/ubuntu-2504-x11-gaming

Reply View 4 replies

thisislife2 5 days ago

I based it on this thread - https://news.ycombinator.com/item?id=46780901

Reply View | 3 replies
- jchw 5 days ago
  
  Latency and throughput are very different things. However, it's worth noting that the comparison here is with and without compositing. If you were using compositing already on X11 (I believe XFCE offers it with "Desktop Effects" or something to that tune) then you've already been eating compositing latency, and you should actually get less latency in some situations.
  But as far as it performing worse overall, I don't think that would be expected. Compositing itself does lean more on hardware acceleration to provide a good experience, though, so if you compare it on a machine that has no hardware accelerated graphics with compositing disabled, then it really would be worse, yeah.
  
  Reply View | 1 reply
  
  mrktf 5 days ago
  
  Little misconception here (beware i'm using xlibre and causal user). On X11 you can find two mechanisms which can be called compositor :
  1st: "enable display compositing" option - this one increases latency as every window draw need go though compositor application (in nutshell it exchanging opengl textures - only synchronization messages goes over "wire")
  2nd: the Xserver rendering pipeline compositor, this one goes with modesetting (intel, amdgpu) driver TearFree option - almost everything inside X11 server in OpenGL textures and compositor perform direct blending to screen (including direct scanout).
  What I want to tell, on modern X (there are merge requests for Xorg server to modesetting driver, amdgpu have this code) with TearFree enabled you by default optimal hardware acceleration - there comes lower latency
  
  Reply View | 0 replies
- happymellon 4 days ago
  
  I don't see any evidence on that thread for anything you said.
  
  Reply View | 0 replies