Xfce's Wayland Compositor Code Continues Improving

[Danielsan]

I remember this wayland compositor is just a concept-proof to see if it is more viable have a compositor in house or reusing another one like wlroots.

[blackshard]

Wayland is the protocol, right. And Weston is reference implementation. Correct me if I'm wrong, but in case of Bitcoin, the reference implementation was ready to use and was actually used. And in case of Wayland, we still get news like this one. I hope it makes my analogy clearer.

No, I don't get it. I don't know why bitcoin is cited here as an analogy so I can't say how much it matches.

Please state clearly what you wanted from Wayland people, because cryptic analogies are not useful.
It looks to me that you are confusing what is a protocol (a set of documents, rules and processes all the parties should agree upon) and what is an implementation of a protocol (the actual code that adheres to such rules and processes).

[oiaohm]

Please state clearly what you wanted from Wayland people, because cryptic analogies are not useful.
It looks to me that you are confusing what is a protocol (a set of documents, rules and processes all the parties should agree upon) and what is an implementation of a protocol (the actual code that adheres to such rules and processes).

Think standard units like a meter. There are in fact physical reference implementations of a meter. Just because you can write documentation what a meter is without a reference implementation how would you know for sure if you have read the documentation right.

Reference implementations like x.org X11 server(its original usage) or Wayland Weston in software exist for the same reason so that a party implementing the protocol find something in the documentation that not clear they look at how the reference implementation implemented it.

Weston is used in automotive and other areas.

Reference implementation while it formally a reference implementation is not allowed to add new features before protocol documentation is written and added to the formal protocol. Welcome to chicken and egg problem.

KDE/Gnome/Sway and others want to be able to write new parts protocol and try them out before doing the process of getting their stuff into the formal protocol.

Lot of mess of x.org X11 server comes about from how often something was added to X11 protocol implemented so it could be added to x.org X11 server then found not to work of course its now added to the X11 protocol so taking it back is kind of hard.

Automotive and other areas using Weston are only after to parts of the protocol that have been peer reviewed.

Desktop and embedded users have very different requirements. Embedded users using Weston are way more conservative.