It really is though. The while GTK/GNOME/systemd/Wayland sandwich is practically control by our IBM/RedHat over lords. They have their tentacles on the entire userspace ecosystem outside the Linux kernel. That was their entire plan. So we can just forget about GTK. Now if Qt and Firefox/Chrome (who are RedHat loyalists) decided to stop future X11 development, FreeBSD is pretty much screwed. We have no control over kwin, mutter, etc.
Unless someone decides to fork gtk2, who's going to maintain it here? The committers aren’t going to bother touching GPLd code outside of drivers. The toolkits and apps are whats at stake here, less so DEs. its either fork the toolkits or write our own Wayland backend for them and browsers.
IMO, I think FreeBSD is ripe for disruption in writing its own API Wayland compositor. The project could penetrate other markets like IoT, embedded, mobile, etc. I’d like a base system I could easily port to ARM/RISC-V phones and tablets. The license, API/ABI stability, and features would fit the concept of Wayland.
Thanks for coming to my TED Talk.