21–30 of 259 posts
Meh. As far as I'm concerned, Wayland is strictly inferior to X, so long as it fails to support network transparency / remoting. Talk to me when they have a real solution for this, besides VNC or supporting RDP.
Earlier quoted context omitted.
After this many years, I think the ambition to support remoting at the per-window level just isn't important. In practice I've actually found it outright confusing when I have two windows operating inside two separate environments, but they're both in the same visual container. VNC/RDP work well enough, and SSH works well enough for when you don't need a GUI.
Both RDP and Citrix do support publishing just the application, without desktop. It is actually pretty neat to have application, running somewhere in the server room, to be mixed with my local applications. Going even further, the remote applications can run each on different machine in the Citrix cluster, so it is possible to load balance on per-app basis.
Earlier quoted context omitted.
It depends on how you define better. VNC may be faster, but it's just because X carries a lot of historical cruft, I believe. Usability-wise, X is more flexible. I can move individual windows between computers in X. I can't do that with VNC. I wouldn't mind doing the jump to Wayland if it were as flexible as X, but that doesn't seem to be the case. Correct me if I'm wrong.
what's the point of running program locally, to be rendered locally, sending the primitives to Xorg server to be displayed somewhere else? is it using Xorg as a network proxy?
Do note that the article is mainly about Wayland on the raspberry pi. Of course Wayland isn't the default most places yet (Fedora being the big exception, I think), though you can install it on most distros. I've been Wayland/Sway on NixOS for a while, and I really like it. One question though - the article seems to say that wlroots is a Rust project, but it seems to very much be a pure C project? ( https://github.co…
Yeah. It uses meson/ninja to build. No Rust.
These manufacturers should be developing proper GPU drivers for mainline with full KMS/DRM/mesa support before they even sell their boards to the public claiming Linux support.
Wayland and Xorg work just fine on Intel integrated graphics, Intel has been setting the standard here for over a decade now.
Earlier quoted context omitted.
Xorg remoting was poorly designed to accomodate DRI/DRM, video card acceleration and had adequate performance to only display primitives on screen. Thats the reasons of poor Xorg remoting adoption. I dont remember seeing anyone in this decade using it - it hands down lost to vnc/nx and rdp.
I've not seen anyone using VNC or remote Xorg for years. Is it really that important these days?
I know of no other method to forward individual programs GUIs to other machines. Abandoning X is abandoning a power we have.
You're right that it may not be used as much. Last time I used it was to debug why selenium tests running in chrome were failing in a server with a virtual display (Xvfb) when the tests would work in any developer's machine. I forwarded chrome's GUI from a docker container in a server in another room via my development machine. Its window was neatly tiled next to my other windows in my tiled window manager. You wouldn't be able to tell it wasn't running locally. I don't have to mess around with a desktop inside a desktop. Such neatness in UX is a comfort I'd like to keep.
I'm all for making a new, more efficient display server, but please don't take powers away.
Earlier quoted context omitted.
what's the point of running program locally, to be rendered locally, sending the primitives to Xorg server to be displayed somewhere else? is it using Xorg as a network proxy?
I think you got it kinda backwards, but due to confusing naming you wouldn’t be the first. It’s more like I’m logging into a remote server (using stuff like SSH), starting applications there and getting the GUI up on my local desktop, like any other local window/app, due to X-forwarding (back to my Xorg server). It’s not perfect, but it sure is a lot more “natural” and integrated into your desktop than VNC or RDP. I…
Meh. As far as I'm concerned, Wayland is strictly inferior to X, so long as it fails to support network transparency / remoting. Talk to me when they have a real solution for this, besides VNC or supporting RDP.
Meh. As far as I'm concerned, Wayland is strictly superior to X, so long as it fails to support keyloggers.
I'd say wayland is just a new thing that breaks everything in an attempt to break less.
I think the author is confusing something here > The reference implementation of the protocol (Weston and it's associated libraries) is written in C. That means you could wrap the C code with Rust, which several people have done already [1] However, I get the impression that the results are not very 'rustic', meaning it's like you are coding C from Rust, instead of writing real Rust code. > To address the problems of…
But yeah, you would still need the C toolchain with this.
Earlier quoted context omitted.
I've not seen anyone using VNC or remote Xorg for years. Is it really that important these days?
The bar for being important enough to not discard when it works and is the only solution to particular problems is not very high. I know of no other method to forward individual programs GUIs to other machines. Abandoning X is abandoning a power we have. You're right that it may not be used as much. Last time I used it was to debug why selenium tests running in chrome were failing in a server with a virtual display (…
A power that literally no one uses.
Well, no one that matters anyway. For values of "matter" equivalent to "uses a modern desktop".
Whatever the case, modern development heavily favors coding for the common case, not supporting a flexible framework that can accommodate fringe cases. And in 2019, your use case is fringe.