| This comment is mostly correct (as a daily Wayland user), with a few exceptions. > Wayland does almost nothing besides render buffer handling. Input? Applications job. Applications don't do more work to handle input on Wayland as opposed to e.g. X11. It's still event-based, and the compositor feeds input events to applications that can process them as normal. Keyboard, mouse and touch input are part of the core Wayland protocol, and tablet input is part of an extension that all major compositors fully support. > Window decorations? Compositors job. Kind of, it's the job of the application (client-side decorations) or compositor (server-side decorations). The compositor can choose which to use. CSDs give more custom look-and-feels to applications that have them (think Firefox or Chrome); SSDs provide consistent looks across all apps. GNOME only supports CSDs, but is an exception in that regard. > Clipboard? Maybe compositor or toolkit. Both: https://emersion.fr/blog/2020/wayland-clipboard-drag-and-dro... Clipboards are (implementation-complexity-wise) scary in X11 as well. |