Thomas Adam<p><a href="https://bsd.network/tags/xorg" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>xorg</span></a> <a href="https://bsd.network/tags/wayland" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>wayland</span></a> <a href="https://bsd.network/tags/windowmanagers" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>windowmanagers</span></a> </p><p>Over on the FreeBSD Forums, I've been postulating what it would mean to have an 'xwayland on xorg' shim, similar to what <a href="https://bsd.network/tags/xwayland" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>xwayland</span></a> does now, just in reverse.</p><p>Why? Because on <a href="https://bsd.network/tags/x11" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>x11</span></a> we have a plethora of decent window managers, and toolkits, most of which won't ever see the light of day any more. Sure, they can live on through <a href="https://bsd.network/tags/wayland" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>wayland</span></a>, but that limits what you'll be able run under that window manager. I think this is <a href="https://bsd.network/tags/wayland" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>wayland</span></a>'s biggest downside -- we're all being funneled through one or two desktop environments. This is going to suck from a UI perspective, IMO.</p><p>I've given this a lot of thought, and I think I want to put myself forward to formally maintain <a href="https://bsd.network/tags/xorg" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>xorg</span></a>. I realise what I'm saying -- and I must be absolutely f***ing crazy, but I think it's the only way if I'm to keep a certain ecosystem alive.</p><p>So... I guess I need to start having conversations with folk over at <a href="https://bsd.network/tags/xorg" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>xorg</span></a> -- sooner rather than later.</p><p>If anyone here can help facilitate that in some formal capacity, that would help.</p><p>I'm very serious about this as well -- but before I look at writing features or anything else, I first need to understand the stupidi^H^H^Hmagnitude of this, and see how I go.</p><p>But I'm putting myself forward to do this.</p>