well here is the brief concept:
it is a markup language for APP (NOT WEB) GUI’s, for Linux
but:
1: it does not have to depend on a single GUI Toolkit (GTK Or QT)
2: it depends on external Programs called “Translators” which translate the Markup language calls and whatever onto something your GUI Toolkit understands
3: it does not manage any form of functionality whatsoever, you have to depend on a another language to do that
what it aims to do:
sometimes a GTK app on a QT Desktop Environment
just does not match the theme
which that idea aims to solve
how would you fix it


Wayland just gives you a buffer to write to, it doesn’t give you drawing primitives in the way XCB does. It’s kinda the point, and makes implementing display servers/compositors a lot simpler and easier, and most apps will be using some kind of non-XCB toolkit anyways.
So if you’re making an app you do kinda need a toolkit, but it can be a very simple and lightweight one.
Not my favorites. I’m mostly thinking of the Suckless sort of tools. dmenu, st, dwm, etc.
But yeah. If a toolkit is necessary for Wayland, then I’d love some extremely minimal options. Or better yet, exactly one minimal option so good that nobody ever feels the need for an alternative. (But that’s not going to happen. Heh.)
I’ve poked a little bit at the Go GUI toolkit “Fyne”. It appears to use OpenGL/GLFW, which is kinda neat, I think. Looks like GLFW’s dependencies are indeed quite minimal.
You can of course just write to the compositor socket directly without relying on any third-party dependency. But it will be very tedious and you will basically end up making your own toolkit (which is coincidentally kinda how GTK started).