Hacker News Reader

XWayland is compartmentalized, and should not make life harder for anyone else in the Wayland world (except the ones spending time maintaining it). And Zink gives us a clean OpenGL implementation on top of Vulkan (so not contributing to complexity in the base stack). I'm fine with a long tail of software requiring XWayland+Zink, and I don't think of them as polluting my system.

View on HN

I think Wayland compositors should start to remove built in Xwayland and rely on tools like xwayland-sattelite for their X compatibility.

Making it easy to run a truly X less compositor and moving X to an optional compatibility layer.

Last time I had a quick look, zink did seem far from being finished, I mean very far away.

The main issues for xwayland+zink are the middle ground applications: those which are x11/vulkan3D without wayland support, if I am not mistaken, like shadow of the tombraider, metro exodus games, etc (even though I would not play anymore those games).

ohohoh... I am going to ask if valheim has a working/tested wayland backend while I am thinking about it.

You probably haven't looked at it for a while. It's a conformant OpenGL implementation. Zink is now the default for Nvidia GPUs in Mesa, replacing Nouveau.

https://www.collabora.com/news-and-blog/news-and-events/good...

Any chance on AMD GPUs? Zink GLX is only for xwayland?

Reply on news.ycombinator.com