4 ms·
> With 'pure Elisp' I mean no FFI. Most Wayland compositors call low-level interfaces to manipulate graphics, but we can not implement such a compositor since t
by generalizations 6y ago
> With 'pure Elisp' I mean no FFI. Most Wayland compositors call low-level interfaces to manipulate graphics, but we can not implement such a compositor since those interfaces are largely absent in Elisp and the performance would be of a great concern. So I tend to make a subcompositor that runs on top of another compositor (mutter for example) to offloads most dirty work and only deals with window management. But even this simplified design can not be realized due to the inability of Elisp to send/receive file descriptors through a socket.
It seems like in this case it's a limitation of elisp, not wayland.
- bsdubernerd 6y agoYou could argue that with emacs modules nowdays you can implement a full compositor by linking-in parts of wlroots if you really wanted to. My point is that you don't have to do any of that in X11 since window-management is implemented through a separate protocol and stand-alone process, which makes it much easier to implement.