"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
Mir’s next steps – we need your input
11–20 of 48 posts
Re: Mir’s next steps – we need your input
#12So 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, bu…
No, Weston is pretty much the reference compositor for Wayland.
Re: Mir’s next steps – we need your input
#13Wayland 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.
What does Mir offer compared to Weston? It still sounds pretty NIH.
Re: Mir’s next steps – we need your input
#14So 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, bu…
Canonical will use Mir on other platforms, I am thinking like the screens that show advertising in Malls or touchscreens that display info and you can interact. from what I read Canonical does not intend to change GNOME too much , only fix the major complains, if they wanted a better system from the code molecularity point of view they had the chance 2 times to use KDE as a base.
Re: Mir’s next steps – we need your input
#15Earlier quoted context omitted.
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…
GNOME devs realized already that they have problems with the current architecture, I think X got the blame though this time too, so they plan a GNOME4 version, I do not know if they started coding it or are just in planing phase.
Re: Mir’s next steps – we need your input
#16"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
https://wiki.gnome.org/Initiatives/Wayland/GnomeShell/GnomeS...
I am not close to the Gnome community, so could somebody aware of the context tell us how serious/realistic/close-term this ideas page is?
Re: Mir’s next steps – we need your input
#17Earlier quoted context omitted.
Wayland is a protocol, Mir will use this protocol, I think you are not uptodate with what is happening here.
What does Mir offer compared to Weston? It still sounds pretty NIH.
Nobody uses Weston, Weston is like the reference thing, each DE is implementing their own compositor. Some DE like Mate hope they can use Mir and so get an easy way to add Wayland support. Ubuntu uses Gnome now so they use Mutter for wayland, Mir would be use for IoT and other non desktop platforms nd there is the possibility that others DE would use it.
Re: Mir’s next steps – we need your input
#18So 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, bu…
No, Weston is pretty much the reference compositor for Wayland.
I tried it. It .. does nothing. Maybe there are/were reference implementations for the protocol extensions too?
Re: Mir’s next steps – we need your input
#19Earlier quoted context omitted.
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.
[deleted]
Re: Mir’s next steps – we need your input
#20So 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, bu…
Canonical will use Mir on other platforms, I am thinking like the screens that show advertising in Malls or touchscreens that display info and you can interact. from what I read Canonical does not intend to change GNOME too much , only fix the major complains, if they wanted a better system from the code molecularity point of view they had the chance 2 times to use KDE as a base.
> Malls or touchscreens that display info and you can interact.
Why would that require anything new? I mean, Canonical is in the server OS business mostly, right?