7 ms·
A Neighbourly Solution to the 'X Is Deprecated? ' Conundrum
- setpatchaddress 6y agoSeems to be an oblique sales pitch for pushing bits of the author's window server architecture into Wayland. Nothing wrong with that, but it didn't really tell me what problem it was trying to solve, nor directly pitch a solution for anything.
- throwaway19937 6y agoThere's really only one appropriate response to nebulous and meandering proposals like this. It's a great idea, now send us a patch.
- acgkmopvvgvmgv 6y agoMaybe I have reading comprehension problems but this article sounds so conflicting and presumptuous. Is it a sales pitch or not? If it is, even when it says it isn't, I would start by looking at Arcan's bus factor, and what refactoring and architectural changes were necessary along the years. Having no expertise in this field I have no patience for people who write in this style but never got involved in the process. But if they did then I would be more interested in reading why their proposal was better and what can be done now in the living code. Also IIUC protocols are exactly that, places to experiment and learn from mistakes until they get stable and anyone can propose them. There are many developers who could write a good technical solution but it's the ones who can deal with the ugly politics that make a real difference. There's a phrase about that there but as always if you don't send code your opinion won't do any good.
- kelnos 6y ago> Maybe I have reading comprehension problems... I was feeling the same! I came away from this article even more confused as to what's been going on. I used to be a maintainer on Xfce (though it's been a decade since I was active), and I've been worried (as a user) about the "upgrade path". Porting (if you can call it that) from X11 desktop environment to Wayland compositor (etc.) is a huge step to take, it seems, and Xfce's current core team doesn't seem interested in going in that direction (I don't blame them). As a user, I want to just keep using Xfce until the heat death of the universe. As someone who might get involved in Xfce development again, I worry that any work I'd be doing on the X11-based things might be wasted time in the long run.
- asveikau 6y agoI seem to recall there was some hacks to get a legacy X11 wm to manage windows for a wayland environment but they were unstable or not maintained. Googling around: xweston and/or xwlnest ?
- acgkmopvvgvmgv 6y agoI wouldn't do that. Only move to Wayland when there is a real path for what you want and need. And it does it without hacks. About porting I would look at what MATE is doing or at the code of Wayland shells, protocols or things like Waybar at GitHub. You don't have to write an entire compositor if you don't want to. Even better get in touch with the people who know what they are talking about, I think they have a wayland IRC channel.
- asveikau 6y agoThere are a lot of unmaintained WMs that work well and are amusing for historical value or retro computing, and probably some of them have a small number of real world users too. I like the idea of a compatibilty layer for those. Maybe not for a big project with ongoing development. But as a last resort to run some cool stuff.
- cycloptic 6y agoIt seems it would be difficult to do that without combining both protocols into one server. (This is not quite what xwayland, xweston, xwlnest do. They run the server X out of process and can't manage wayland windows because they don't know anything about the internal wayland state) To that point, you would have to decide if it's more worth it to fork xwayland and merge with an existing wayland compositor, or to fork xfree86 and add wayland.
- csande17 6y agoI bet you could achieve it with three layers. First, run a "top level" Wayland compositor. Then, use XWayland to run an X session (with your favorite window manager). Then, use Weston's X client mode to run Wayland applications inside the X session. As silly as that sounds, it might actually be a good solution. Red Hat gets to push their shiny new display server protocol, and I still get to make screen recordings and use my favorite window manager. I wonder how well it works in practice...
- crazyloglad 6y agoIt is a compromise for how Xorg and Wayland can have a shared graphics backend that improves both sides and the part that the Xorg maintainer wants gone can go away. Arcan has had its own fork of Xorg for many years, as well as a Wayland implementation. Nothing here will change that trajectory. The library mentioned is about ~2kloc, decoupled from the rest of the project (100+kloc) and the relevant subset has not changed significantly for several years.
- pronoiac 6y agoThis is about X.org deprecation, which has come up a bit this week: * "The X.Org Server Is Abandonware" / https://www.phoronix.com/scan.php?page=news_item&px=XServer-Abandonware https://www.phoronix.com/scan.php?page=news_item&px=XServer-... / https://news.ycombinator.com/item?id=24884988 https://news.ycombinator.com/item?id=24884988 * "on abandoning the X server" / https://ajaxnwnk.blogspot.com/2020/10/on-abandoning-x-server.html https://ajaxnwnk.blogspot.com/2020/10/on-abandoning-x-server... / https://news.ycombinator.com/item?id=24920183 https://news.ycombinator.com/item?id=24920183
- tpoacher 6y agoYes, if I didn't know better I'd say someone is trying to create news.
- bitwize 6y agoAuthor misses the point. > There are strong differences that will not get smoothed over regardless of how many 'protocols' you define; Wayland is Policy over Mechanism, X11 is Mechanism over Policy. Why yes, that's the whole point. I don't know if you've noticed, but "policy over mechanism" has thoroughly won in the desktop space. The dominant desktop is Windows; even macOS has several times the mind/market share that Linux has. This is pretty much the "Emacs modernization" debate for the desktop as a whole. There is a growing contingent of Emacs users who saw their chosen editor get its lunch eaten by Visual Studio Code, and now wish it was a bit more modern and a bit less... well, less Emacs. Similarly, Wayland was pushed by a large contingent of users who want to see the Linux desktop resemble a successful desktop used by millions to get their work done. Back when GUIs were brand new and the Unix community was populated by neckbeards, creativity and experimentation in the desktop space was a good thing. Today, those neckbeards have grown older. Time for them is shorter. So even they don't want to experiment anymore; like everybody else they just want to get their fucking work done. Millions of people have gotten work done with the successful model of Windows and Mac, and Linux users want their desktop to resemble the most successful desktops of all time -- not something that is a large pile of hack upon hack with seams constantly showing. Pushing back against the direction the ecosystem is going will only breed resentment and ill will, because you are committing time and brainpower to a dead end when you could have committed it to making Wayland better.
- crazyloglad 6y ago> I don't know if you've noticed, but "policy over mechanism" has thoroughly won in the desktop space. The dominant desktop is Windows; even macOS has several times the mind/market share that Linux has. Windows exposes lots of WM mechanisms to a developer, hence why something like vrdesktop.net could be built in the first place, or previous WMs like LiteStep for that matter. It is also why WINE does not, and cannot, have a working Wayland backend while sticking to the protocol. The same is true for X, but there XWayland requires the compositor developer to implement a sideband window manager to hack around the entire Wayland protocol to get X clients to work.
- cycloptic 6y ago
- eximius 6y agoWhat is holding Wayland back? Was the core protocol just not created with many basic features in mind?
- izacus 6y agoIt's created with a different core approach and architecture, so you can't just change API calls in some software to support it. Whole new pieces of software have to be written using a different approach (mainly around keyboard event, clipboard, remote access and screen recording features).
- rcxdude 6y agoThe core protocol was designed to be much simpler and more representative of modern graphics hardware (basically just a way for applications to get a buffer they can throw their pixels onto, which is then composited onto the screen, and passing of keyboard and mouse events to the application only when it's actually focused). Partly the issue has been getting good support for this in drivers and applications, and partly the issue is the base protocol doesn't allow for a bunch of features by default (a lot of which in X were essentially massive security holes, since any X client can take screenshots, intercept keyboard/mouse events globally, etc). These features are being added, but it seems as custom extensions in each compositor without widespread support.
- eximius 6y agoI see. wf-recorder is specific to wlroots, etc. I suppose I'm sad that these things weren't upstreamed to the core protocol/reference impl sooner so there was less churn.
- jjt-yn_t 6y agoWhat annoys me a bit in these articles/threads is the lack of info about which video cards are suited for either Xorg or Wayland... or conversely not...