9 ms·

I've also been using wayland for a couple years now. Switched from i3 to sway and never had screen tearing as I did with X server. Just recently moved to Hyprl

by talhah 3y ago

I've also been using wayland for a couple years now. Switched from i3 to sway and never had screen tearing as I did with X server. Just recently moved to Hyprland and similar experience. Barely had any hiccups and switching to a non-english layout such as Arabic works like a charm. Perhaps maybe our systems are just ideal? For the record I'm using a thinkpad which generally has good support but even on my Lenovo G505 it worked perfectly.

LoganDark 3y ago
GNOME supports my trackpad better than Windows and, dare I say it, macOS does. As in, it literally supports trackpad gestures and inputs that Apple doesn't, and it's actually really smooth and responsive. You can right-click-drag, and you can middle click. macOS doesn't support either one of these, and Windows only supports assigning a bottom-right quadrant of the trackpad to right-clicking.
- thewataccount 3y ago
  I wish there was an equivalent to "better touch tool" for linux, that program adds so many trackpad/other peripheral shortcuts and gestures it's crazy and doesn't involve editing config files from a wiki and half a dozen stack overflow pages.
- mort96 3y ago
  GNOME has the fatal flaw that you can't configure trackpad scroll sensitivity. That means, if your trackpad is too sensitive out of the box, GNOME is simply unusable. Every laptop I've used in the past many years (a couple of Dells and a Mac) have had touch pads with too sensitive scrolling in GNOME. It's fine in Sway or KDE, as they have scroll sensitivity settings.
  - LoganDark 3y ago
    > GNOME has the fatal flaw that you can't configure trackpad scroll sensitivity. Oh, I got bitten by that actually. I ended up just configuring Firefox since that was the main app I used, but most apps aren't Firefox and don't have settings for things that they would expect to be handled by your WM/DE/DM.
  - kaba0 3y ago
    AFAIK it is a fundamental GTK problem, so Sway or KDE can only circumvent it for GTK apps.
    - mort96 3y ago
      I don't believe it's a fundamental GTK problem. When you scroll, the Wayland compositor sends scroll events to the app, with a float for the delta. KWin and Sway have an option to let you multiply that delta with a constant; multiply it by 0.5 and you have halved your scroll speed. GNOME doesn't have such an option. GTK may have other scroll issues as well (I recall seeing some stuff about that, though I don't remember the details), but there is definitely stuff the compositor can do.
      - kaba0 3y ago
        > When you scroll, the Wayland compositor sends scroll events to the app, with a float for the delta GTK works through a bunch of heuristics and in-built multipliers, but the fundamental problem is that scroll effect depends on the “weight” of the content itself — kinematic scrolling is unfortunately quite missing from linux desktop, AFAIK. But do correct me if you know better, I’m not too well versed in that.
BrotherBisquick 3y ago
I can never go back to X11 and I think the greatest condemnation of it is that we're still talking about screen tearing in 2023. Screen tearing is something that simply shouldn't exist by default. A person should be able to count on its absence, like a person should be able to count on a basic USB keyboard working without any headaches. Now I'll brace myself for the "I've never noticed screen tearing" from people whose brains run on a different refresh rate than mine does.
- dontlaugh 3y ago
  I don’t get how some people don’t see it. I remember running a very weird compiz setup just to alleviate screen tearing, many years ago. It was such a relief the first time I used Mac OS X. Finally a unix that renders to the screen without artifacts.
  - p_l 3y ago
    Because screen tearing is something that honestly showed up pretty late, around the time of i3/i5/i7 with IGP, as before that tearing was mitigated at least a little with VSync. (There's the issue that X11 didn't expose good sync primitives, but that's workable with extension, not total replacement)
    - dontlaugh 3y ago
      Even with vsync it happened on X11 on dedicated GPUs. Plus a number of other buffer management artefacts. It didn’t help that the drivers for everything were closed course, but even with perfect drivers X11’s design can’t deliver perfect frames.
      - p_l 3y ago
        The design can deliver perfect frames - it's extensible so pretty much you need to provide a way to handle double buffering right - and guess what, extensions for that were proposed (Present extension by Keith Packard, building on top of X Synchronization extension)

by talhah 3y ago

LoganDark 3y ago

GNOME supports my trackpad better than Windows and, dare I say it, macOS does. As in, it literally supports trackpad gestures and inputs that Apple doesn't, and it's actually really smooth and responsive. You can right-click-drag, and you can middle click. macOS doesn't support either one of these, and Windows only supports assigning a bottom-right quadrant of the trackpad to right-clicking.

thewataccount 3y ago
I wish there was an equivalent to "better touch tool" for linux, that program adds so many trackpad/other peripheral shortcuts and gestures it's crazy and doesn't involve editing config files from a wiki and half a dozen stack overflow pages.
mort96 3y ago
GNOME has the fatal flaw that you can't configure trackpad scroll sensitivity. That means, if your trackpad is too sensitive out of the box, GNOME is simply unusable. Every laptop I've used in the past many years (a couple of Dells and a Mac) have had touch pads with too sensitive scrolling in GNOME. It's fine in Sway or KDE, as they have scroll sensitivity settings.
- LoganDark 3y ago
  > GNOME has the fatal flaw that you can't configure trackpad scroll sensitivity. Oh, I got bitten by that actually. I ended up just configuring Firefox since that was the main app I used, but most apps aren't Firefox and don't have settings for things that they would expect to be handled by your WM/DE/DM.
- kaba0 3y ago
  AFAIK it is a fundamental GTK problem, so Sway or KDE can only circumvent it for GTK apps.
  - mort96 3y ago
    I don't believe it's a fundamental GTK problem. When you scroll, the Wayland compositor sends scroll events to the app, with a float for the delta. KWin and Sway have an option to let you multiply that delta with a constant; multiply it by 0.5 and you have halved your scroll speed. GNOME doesn't have such an option. GTK may have other scroll issues as well (I recall seeing some stuff about that, though I don't remember the details), but there is definitely stuff the compositor can do.
    - kaba0 3y ago
      > When you scroll, the Wayland compositor sends scroll events to the app, with a float for the delta GTK works through a bunch of heuristics and in-built multipliers, but the fundamental problem is that scroll effect depends on the “weight” of the content itself — kinematic scrolling is unfortunately quite missing from linux desktop, AFAIK. But do correct me if you know better, I’m not too well versed in that.

BrotherBisquick 3y ago

I can never go back to X11 and I think the greatest condemnation of it is that we're still talking about screen tearing in 2023. Screen tearing is something that simply shouldn't exist by default. A person should be able to count on its absence, like a person should be able to count on a basic USB keyboard working without any headaches. Now I'll brace myself for the "I've never noticed screen tearing" from people whose brains run on a different refresh rate than mine does.

dontlaugh 3y ago
I don’t get how some people don’t see it. I remember running a very weird compiz setup just to alleviate screen tearing, many years ago. It was such a relief the first time I used Mac OS X. Finally a unix that renders to the screen without artifacts.
- p_l 3y ago
  Because screen tearing is something that honestly showed up pretty late, around the time of i3/i5/i7 with IGP, as before that tearing was mitigated at least a little with VSync. (There's the issue that X11 didn't expose good sync primitives, but that's workable with extension, not total replacement)
  - dontlaugh 3y ago
    Even with vsync it happened on X11 on dedicated GPUs. Plus a number of other buffer management artefacts. It didn’t help that the drivers for everything were closed course, but even with perfect drivers X11’s design can’t deliver perfect frames.
    - p_l 3y ago
      The design can deliver perfect frames - it's extensible so pretty much you need to provide a way to handle double buffering right - and guess what, extensions for that were proposed (Present extension by Keith Packard, building on top of X Synchronization extension)