If the hardware provides the luxuary of "presentation" (~vblank) control, an application has to query the appropriate "presentation" wayland interface... namely the application must not expect this interface to be around.

You can see that in vulkan3d with its presentation queue: you post your pixels and forget about it (but there are extra presentation interface beyond the core interface like in wayland).

It through away everything many knew about rendering timing... for very good reasons, aka not planned obsolescence. This is why many are "wtf" about core wayland. Yes, we reached a point in software where innovation means removing and simplifying, not adding and complexifying.

The cherry on top: it makes the wayland core interfaces sooo much simpler, one dev can quickly have a working alternative implementation, and grow it step by step with luxuary extra interfaces.

I say that, I am still running good old native x11, because I game on elf/linux (#noproton), but the second the steam client drops its 32bits legacy code and have a working wayland backend, I start to code my own wayland compositor, probably based on the drm/vulkan one from valve deck, but in plain and simple C, or straight to x86_64 assembly (lurking on RISC-V ofc, since porting modern assembly ISAs is brutal but far from being hard).