[HN Gopher] Wayland *Sucks
       ___________________________________________________________________
        
       Wayland *Sucks
        
       Author : Jkvngt
       Score  : 13 points
       Date   : 2021-01-28 20:01 UTC (3 hours ago)
        
 (HTM) web link (magnushoff.com)
 (TXT) w3m dump (magnushoff.com)
        
       | snicker7 wrote:
       | (2018)
        
       | intsunny wrote:
       | Please add (2018) to the title.
        
       | mixmastamyk wrote:
       | What is the state in 2021?
        
         | oehtXRwMkIs wrote:
         | I have never used GNOME and I've never experienced any of these
         | issues.
        
           | 3836293648 wrote:
           | GNOME has an input lag issue due it being handled on the same
           | thread as everything else. This has been fixed for GNOME 40
        
       | Barrin92 wrote:
       | the last negative point is something I noticed. Wayland somehow
       | seems to handle the cursor on the same thread as anything else,
       | meaning when your system is under heavy load the cursor actually
       | starts to lag, and even under normal circumstances mouse movement
       | feels weirdly laggy. It is an absolutely atrocious experience,
       | like someone has put sand on your toothbrush or something, it
       | actually makes Wayland unusable for me.
        
         | mixedCase wrote:
         | Are you using GNOME? I've never had that happen under Sway and
         | I remember reading many GNOME users' complaints about exactly
         | that.
        
           | Barrin92 wrote:
           | yep I'm on Gnome. Maybe I'll give sway a shot, I used i3 a
           | few years ago.
        
         | flukus wrote:
         | Yep, when I last had a memory leak (kayo in case anyone here
         | works on it) it would refuse to process input. Couldn't close
         | the offending tab with the mouse, couldn't switch to a
         | terminal. All I could do was reach for the hard reset button.
        
         | johnny22 wrote:
         | that's a problem with the specific compositor (DE/WM) you're
         | using. If it's GNOME you're referring to, then that should be
         | fixed in the next release. If it's something else, you'll have
         | to check with them.
        
         | [deleted]
        
       ___________________________________________________________________
       (page generated 2021-01-28 23:02 UTC)