• twinnie@feddit.uk
    link
    fedilink
    arrow-up
    6
    ·
    4 days ago

    VMware Player still can’t copy and paste properly between the two machines on Wayland. How on earth is that affected by the desktop compositor?

    • dismay3915@lemmy.world
      link
      fedilink
      arrow-up
      6
      arrow-down
      1
      ·
      4 days ago

      One problem here lies within the architecture of wayland that it forces every DE/WM to implement their own compositing and many other things. So more and more fragmentation and harder for both WM developers and app developers.

      • bobo@lemmy.ml
        link
        fedilink
        arrow-up
        1
        ·
        edit-2
        2 days ago

        One problem here lies within the architecture of wayland that it forces every DE/WM to implement their own compositing and many other things.

        https://github.com/solarkraft/awesome-wlroots#compositors

        Compositors built on it like river

        River is a non-monolithic Wayland compositor. Unlike other Wayland compositors, river does not combine the compositor and window manager into one program. Instead, users can choose any window manager implementing the river-window-management-v1 protocol.

        Lxqt allows you to choose a different Wayland compositor (work in progress).