> No, what we are saying is that *in the general case* you are better off rendering your application client-side and pushing (compressed) bitmaps over the network, and if in a *specific use case* that isn't good enough, you are better of using (X)HTML rather than reimplementing it poorly in the compositor...
That "XHTML" is called XRender and was invented in X almost 15 years ago. It supports primitives, gradients, even some transformations. It allows you something like drawing a page of text in one command without sending any images, just referencing previously sent glyphs. Uses hardware acceleration if possible. And all modern toolkits know about it.
X also allows you to display anything locally, even directly talking to hardware with mesa, like on Wayland.
There's no need to reinvent it for Wayland, it's already done for X.