Mir’s next steps – we need your input
community.ubuntu.com
Mir’s next steps – we need your input
1–10 of 48 posts
Re: Mir’s next steps – we need your input
#2So Mir will become a Wayland compositor?
Re: Mir’s next steps – we need your input
#3Wayland was already there, and there was nothing wrong with it. OK, maybe there was, but not the bullshit you made up to justify your NiH syndrome alternative.
Mir was pointless. Drop it. It should never have existed in the first place.
Re: Mir’s next steps – we need your input
#4Wayland was already there, and there was nothing wrong with it. OK, maybe there was, but not the bullshit you made up to justify your NiH syndrome alternative. Mir was pointless. Drop it. It should never have existed in the first place.
If I understand correctly, they'll drop the server part replacing it with Wayland. But they'll keep their compositor, which any Wayland based DE needs to implement anyway. They don't intended it for the desktop, since they are dropping Unity. It's for IoT and etc.
Re: Mir’s next steps – we need your input
#5So Mir will become a Wayland compositor?
Yes
Re: Mir’s next steps – we need your input
#6Wayland was already there, and there was nothing wrong with it. OK, maybe there was, but not the bullshit you made up to justify your NiH syndrome alternative. Mir was pointless. Drop it. It should never have existed in the first place.
Wayland is a protocol, Mir will use this protocol, I think you are not uptodate with what is happening here.
Re: Mir’s next steps – we need your input
#7Wayland was already there, and there was nothing wrong with it. OK, maybe there was, but not the bullshit you made up to justify your NiH syndrome alternative. Mir was pointless. Drop it. It should never have existed in the first place.
If I understand correctly, they'll drop the server part replacing it with Wayland. But they'll keep their compositor, which any Wayland based DE needs to implement anyway. They don't intended it for the desktop, since they are dropping Unity. It's for IoT and etc.
They can't replace something with Wayland because Wayland is a protocol and interface, Mir needs to implement code to speak that protocol.
Re: Mir’s next steps – we need your input
#8"This is where server/compositor/window manager and panels/docks/desktop are all in a single process."
This sounds like gnome-shell, and it's atrocious. It's unresponsive and laggy under any sort of load, even the mouse cursor skips around
Re: Mir’s next steps – we need your input
#9Wayland was already there, and there was nothing wrong with it. OK, maybe there was, but not the bullshit you made up to justify your NiH syndrome alternative. Mir was pointless. Drop it. It should never have existed in the first place.
If I understand correctly, they'll drop the server part replacing it with Wayland. But they'll keep their compositor, which any Wayland based DE needs to implement anyway. They don't intended it for the desktop, since they are dropping Unity. It's for IoT and etc.
I hardly think that Mutter is the be-all and end-all of Wayland compositor performance. I could see Ubunu plumbing a re-moulded Mir back into their distribution further down the line (while keeping the rest of the GNOME environment). I'm not certain on the technical details, but I believe this should be possibly; for Wayland was certainly designed with compositor agnosticism in mind.
Edit: reading further, it appears that GNOME Shell is quite tightly woven into Mutter, which may well complicate matters.
Re: Mir’s next steps – we need your input
#10So X was horrible, because it is very old and blablabla, and Wayland the protocol got finalized without an actual implementation that people use in good old design by committee fashion (no?), and for some reason now everybody writes compositors instead of writing one for Linux in general... I don't really understand why, can someone explain? (I mean, I know about how Mir seemed to be regular Canonical NIH symptom, but why are they continuing with it?)