Mir’s next steps – we need your input

Re:Mir’s next steps – we need your input by AdmiralAsshat on Wednesday November 22, 2017 @02:44PM (#15759867)

At the very least, get Mir to the point where it's a drop-in replacement for Weston, the reference Wayland compositor. Then make whatever changes you feel like on top of that. If Mir becomes included in DE's across various distros, and if it becomes a runtime option when launching a session (in the same way that GNOME now lets you choose whether to run a Wayland or Xorg session at login), people will be able to A/B test Mir vs Weston, they'll send feedback, and the improvements can be upstreamed.

That's all I ask. The backlash against Canonical was in leveraging the Open Source community to make increasingly silo'd services. Canonical is moving in the right direction, first in discontinuing Unity in favor of GNOME, and now in making Mir Wayland-compatible. I hope the trend continues.

[ Parent | on HN ]

Re:Mir’s next steps – we need your input by majewsky on Wednesday November 22, 2017 @03:43PM (#15760433)

I think there's some misunderstanding in your comment about how Wayland works. 99.9% of Wayland desktops out there [1] do not use Weston. Weston is not Wayland's display server, it's a reference implementation of a window manager implementing the Wayland protocol(s). There is no separation between display server and window manager in Wayland, only a single master process, the compositor, which fulfils (roughly) both these roles. So if you're running, say, KDE Plasma, then your compositor is KWin, and Weston is nowhere to be seen. If you're running Sway, then your compositor is Sway. And so on. Wayland is only a protocol, not a piece of software (unless you count the shared libraries provided by the Wayland project).

[1] Guesstimate.

[ Parent | on HN ]