That said, I feel that Wayland devs (and users) are just now (re)learning the ecosystem catch-22 problem. The ecosystem hasn't caught up with Wayland's new architecture because the layers don't line up the same way. This means entirely new layers (or adapters) need to be created all the way up the stack.
Also, this new design and these interfaces are almost completely undocumented, so it makes it very hard for a non-waylander to step in and contribute. I made a couple attempts to fix bugs, but after wading through Github issues for 4 hours, and getting no help on IRC, I gave up.
Unfortunately the ecosystem is responsible for building the rest of the stack, but it's hard, because there isn't much in the way of documentation or examples in the ecosystem. That's the catch. The ecosystem is expanding very slowly because there isn't much of an ecosystem.