Tweet
Yay, we now have something X11 had in 1988 ...
-
-
Mir is just a shitty wayland compositor in that regard. You shouldn't need it and if it does need it that's just more shitty vendor lock in.Originally posted by starshipeleven View Post
But lets not kid ourselves all Mir was ever about was Ubuntu gaining some vendor lock in....Last edited by cb88; 17 December 2019, 11:00 AM.Comment
-
Which display server would you suggest that the MATE project and the UBports project use in place of Mir? And are you willing and able to help those projects port to your suggested display server?Originally posted by cb88 View PostComment
-
Do you know how Wayland works? You do need a compositor.Originally posted by cb88 View PostComment
-
This feature is about the compatibility mode for Xorg applications. (Xwayland)Originally posted by Raka555 View Post
It's worth comparing it with other Wayland compositors.
Comment
-
Mir isn't the only compositor on the block... why would I want to use any software designed to lock me into their ecosystem on top of an open protocol...Originally posted by starshipeleven View PostComment
-
It is the most fully-featured one apart from Kwin and Mutter, which apparently none outside of KDE and GNOME want to touch.Originally posted by cb88 View Post
Because you don't have the manpower to make your own, or add functionality you need to other compositors.why would I want to use any software designed to lock me into their ecosystem on top of an open protocol...
But as it is, none of the MATE team is really working on Mir/MATE integration (any example was shown by Ubuntu/Mir developers), they are probably not going to care about wayland for a long while still.
Comment
-
Agree with (and liked) the other bits from your comments. But regarding MATE's involvement, I'll just note that Martin Wimpress and Alan Pope (co-founders of Ubuntu MATE) are both Canonical employees, as is William Wold, who's doing most of the work to implement Wayland support on MATE via Mir.Originally posted by starshipeleven View Post
Also, back in 2017, Martin Wimpress stated:
So it seems that there's some collaboration happening.The rumors of Mir's death are greatly exaggerated. MATE is a very small team, with extremely constrained time. Implementing Wayland directly is, at our current development velocity, several years away IMO. If Mir could provide us a fast path to supporting Wayland we (and possibly other desktops without Wayland support) should explore it....Using Mir as the Wayland compositor, while still a chunk of work, is considerably less work.
William Wold, who's doing most of the work to implement Wayland support on MATE via Mir, stated:Originally posted by cb88 View Post
The default MATE Wayland session will run Mir, but nothing in MATE should be tightly coupled to it. We want it to be possible to run all the pieces of MATE inside any compositor you wish. This is why we adopted the wlr-layer-shell protocol that came out of wlroots, and will probably use wlr-foreign-toplevel-management as well. We're on good terms with the wlroots developers, and work with them whenever it makes sense. We're committed to improving the Wayland ecosystem in general (not just for Mir based compositors).Comment
-
It's been a while, so they might have changed their minds, but, last I checked, the LXQt people were tentatively planning to use KWin for Wayland.Originally posted by starshipeleven View PostComment
-
Good to know. They are the only ones that seem to care about Wayland then.Originally posted by ssokolow View Post
Comment
Comment