Title

  • pathief@lemmy.world
    link
    fedilink
    arrow-up
    9
    arrow-down
    1
    ·
    11 months ago

    I think the main problem is that Wayland is not a drop in replacement.

    Every software needs to support Wayland, new environment flags need to be created, flags must be used with electron apps…

    Nvidia support has been spotty and some functionality has not yet been implemented. I use a custom .xcompose file, which doesn’t work on electron apps. Let me know if there’s a better way to mimic window’s dead keys.

    Overall, it’s hard for an end user to change from a solution that is working perfectly to a solution that requires a ton of work and doesn’t yet have the same functionality.

    Everyone can understand that Wayland is the future but depending on your needs and hardware the current experience can be great or terrible.

    • Auli@lemmy.ca
      link
      fedilink
      English
      arrow-up
      4
      arrow-down
      2
      ·
      11 months ago

      Sure but as someone starting with a new system Wayland just works. Example multitouch works right away on Wayland and if I remember correctly needs configuration on x11.

      • pathief@lemmy.world
        link
        fedilink
        arrow-up
        5
        ·
        11 months ago

        “just works” depends on your needs. There is. Polarizing opinion on the Wayland vs x11 because the experiences are also very polarizing.

      • pathief@lemmy.world
        link
        fedilink
        arrow-up
        1
        ·
        11 months ago

        I had to set a ton more. Without the ozone flags my electron apps flicker and have this sync problem that appears to eat letters while I type them. Different electron apps use different configuration files, it’s a mess.

        I wouldn’t consider my setup to be complex enough for the amount of trouble I had to make the system work under Wayland.

        I’m using an Nvidia GPU, I’m sure things would be more streamlined if I had something else.