Every frame is perfect requires extreme amounts of coordination. Frequently multiple buffering, which increases latency and increases latency. All these are costs which most use-cases don't care about.
Under normal conditions, with display managers that don't care, frames are extremely rarely "not perfect". And when they aren't perfect they are seldom "not perfect" for more than a single frame.
This is a fine example of "the perfect is the enemy of the good"
Did you try viewing a full screen video on X without a compositor? Even though today’s video hardware is indeed fast enough to mask it more often than not, display technology also requires more and more resources — I am sure you will find plenty of tearing at larger than 1080p resolution and higher framerate.
And come on, how is it extreme amounts of coordination? That’s like the most basic coordination there is. Especially that it can be circumvented in the rare case it is not needed — e.g. game windows in full screen can render at their heart’s content.
Wat. https://www.x.org/releases/X11R7.5/doc/man/man3/XQueryExtens...
X is full of extensions. Even extensions that the server does not need to worry about, e.g. EWMH [0] because the protocol is flexible enough to support that.
[0] https://specifications.freedesktop.org/wm-spec/wm-spec-1.3.h...
Wayland was literally made with the explicit intent of providing extensions and they are a core part of the protocol — a client app is free to query the available protocols with versions, while there was nothing similar to that under X.
And really, “every frame is perfect” of a display manager managing.. frames is somehow strange? Would it be strange for a video player as well?