Felix Palmen :freebsd: :c64:<p><span class="h-card" translate="no"><a href="https://bsd.network/@thomasadam" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>thomasadam</span></a></span> <span class="h-card" translate="no"><a href="https://fosstodon.org/@peppe" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>peppe</span></a></span> Thanks for that! I totally forgot about the decorations topic, which is of course very relevant, it means even jumping through the hoop and implementing a <a href="https://mastodon.bsd.cafe/tags/wayland" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>wayland</span></a> compositor, you can only deliver part of the functionality (and almost none of the looks) of your window manager.</p><p>But even with that issue solved, I would really dislike wayland's design. Although I *do* think that most of <a href="https://mastodon.bsd.cafe/tags/X11" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>X11</span></a> core drawing is obsolete and useless (mostly for the missing alpha channel), I think a display server should offer drawing facilities. Replace X with something dropping lots of cruft (indexed palettes, COMPOUND_TEXT, etc), instead incorporate extensions that everyone needs these days, extend <a href="https://mastodon.bsd.cafe/tags/XRender" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>XRender</span></a> (now as part of core) to offer more drawing primitives, etc ... you could have a replacement for X11 that's worth dealing with. And window managers could still be separate clients.</p>