It can be if one wants to. For example river has its own protocol for letting clients arbitrarily position windows. There's a builtin one that does tiling, and then a bunch of user-created ones at https://codeberg.org/river/wiki/src/branch/master/pages/Comm...

But yes, it requires such extensibility support from the compositor, unlike this project that works with any X11 compositor because it just relies on EWMH.

It seems like it's reinventing (an partial, incomplete, non-standard) Xorg protocol on top of Wayland, while we can simply use X11

For now... but it is mostly unmaintained at this point and it is only a matter of time before it starts breaking if no one takes over. Which looks doubtful.

You can implement hot corners on Wayland using layer-shell and creating a 1px transparent surface on each monitor corner.

Can you? I grant that you can probably trigger like that, but does Wayland have a generic way to move+resize windows?

> does Wayland have a generic way to move+resize windows?

I'm not entirely sure what you mean here or how it is related to hot corners.

The compositor itself can move windows anywhere (it is in full control). A client moving the windows of other clients is not permitted, although compositor-specific interfaces exist for this. There's no standard here because a stacking compositor implements completely different semantics from a tiling compositor. I'm sure that protocol extensions will come up for niche use cases over time.

I thought about this and came to a conclusion, that it should be possible, though not exactly easy, to implement a Wayland compositor that speaks enough X11 to run an X11 Window Manager which would position Wayland windows, while not nullifying the whole security angle of Wayland.

At that point you're slowly going to rebuild X11 except without XFree86 baggage and with some extensions (like extensive security that some servers provided) included whereas XFree86 (and tbqh, wayland) come from the land of "first step, disable selinux"