3 ms·
What is holding Wayland back? Was the core protocol just not created with many basic features in mind?
by eximius 6y ago
What 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.