• nitrolife@rekabu.ru
    link
    fedilink
    arrow-up
    1
    arrow-down
    1
    ·
    11 months ago

    Eh, the era when it was possible to throw the interface through an SSH session is over. Sadly. Or maybe I’m just too old. XD

      • nitrolife@rekabu.ru
        link
        fedilink
        arrow-up
        2
        ·
        edit-2
        11 months ago

        Thanks. Not full wayland protocol support and have a bugs, but something is greater than nothing. UPD: The utilization of the Internet channel has also increased

        • arc@lemm.ee
          link
          fedilink
          arrow-up
          5
          ·
          11 months ago

          If you look at any modern desktop application, e.g. those built over GTK or QT, then they’re basically rendering stuff into a pixmap and pushing it over the wire. All of the drawing primitives made X11 efficient once upon a time are useless, obsolete junk, completely inadequate for a modern experience. Instead, X11 is pushing big fat pixmaps around and it is not efficient at all.

          So I doubt it makes any difference to bandwidth except in a positive sense. I bet if you ran a Wayland desktop over RDP it would be more efficient than X11 forwarding. Not familiar with waypipe but it seems more like a proxy between a server and a client so it’s probably more dependent on the client’s use/abuse of calls to the server than RDP is when implemented by a server.

        • LeFantome@programming.dev
          link
          fedilink
          arrow-up
          3
          ·
          11 months ago

          What kind of bugs are you running into? The original Waypipe proposal claimed that it was pushing less data than X. Let’s hope it gets faster in the future.

          • nitrolife@rekabu.ru
            link
            fedilink
            arrow-up
            1
            ·
            11 months ago

            Short command wasn’t work in my env. I can run only with full sockets path. May be I do something wrong.