Linux
Welcome to c/linux!
Welcome to our thriving Linux community! Whether you're a seasoned Linux enthusiast or just starting your journey, we're excited to have you here. Explore, learn, and collaborate with like-minded individuals who share a passion for open-source software and the endless possibilities it offers. Together, let's dive into the world of Linux and embrace the power of freedom, customization, and innovation. Enjoy your stay and feel free to join the vibrant discussions that await you!
Rules:
-
Stay on topic: Posts and discussions should be related to Linux, open source software, and related technologies.
-
Be respectful: Treat fellow community members with respect and courtesy.
-
Quality over quantity: Share informative and thought-provoking content.
-
No spam or self-promotion: Avoid excessive self-promotion or spamming.
-
No NSFW adult content
-
Follow general lemmy guidelines.
view the rest of the comments
You assume I'm not using it. On the contrary, I use it a lot at work. We have some old TK interfaces. They take ages to load over the network. The interfaces load much faster when using Xvnc running on the remote machine rather than X forwarding (but it is not as convenient).
@hummus273 Xvnc does not allow you to display individual applications only an entire desktop. I'm monitoring about 20 different computers doing different things and for me it is a significant advantage not to have to bring up a whole desktop but to be able to launch a single graphical application on my existing desktop.
I don't really understand the degree of emotional attachment people have to one solution or another. For me it's a simple application case, for me Wayland is not desirable, not only does it not network, but the embedded X-server as part of the kernel works very effectively by avoiding the kernel/userland switches an ordinary X server would require.
So for my use case, Wayland is NOT a replacement and so I have to object to people arguing that it is a full replacement for X, it is not.
Yes, that is what I meant with not as convenient.
Your use case is covered by waypipe (which in my tests is much more responsive than X11 forwarding).
I think you are confusing stuff here. Which kernel has an embedded X server?
What part of your use case is not covered by waypipe?
@hummus273 Waypipe would involve a lot of userland / kernel exchanges avoided by using the kernel based mode setting Xserver. It happens to work well with my hardware. And I don't see any noticeable latency issues and not all apps work with Wayland hence I have no motivation to change to Wayland and every motivation to avoid it. Sorry if that gets someone's panties in a wad.
Waypipe has nothing to do with the kernel mode setting driver. The X server code does not run in the kernel. Wayland compositors use kernel modesetting for mode changes, so not sure what your point is? Not saying you need to switch to Wayland, just saying that it covers the use case you described as impossible with Wayland.
@hummus273 Yes actually in my case it does. The kernel has an X-server built in but ONLY for Intel graphics and I happen to have Intel graphics. Sorry if you're not familiar enough with X or the kernel to know that but that is a fact.
If that is the case, then you can probably easily find the X server code in the Linux kernel and send a link? Spoiler: it is not there
@hummus273 I am mistaken, it is only the mode setting for the X-server that is handled in the kernel. At any rate it works well for my needs.