CMake is something optional (I like it), but C++ is the highest level you could use for something like that, I wouldn't be that glad just because there wasn't really any choice there. I don't think that makes it any better than any other display system per se.I am glad they are using pure c++ and Cmake system.
There are more of political and business competition decisions than real technical decisions. It is just sad to see that the "linux community" let themselvs utilize for that game. Technically it should be: let them all do their work and we will see what is best in the end.
Because the "Linux community" is more inteligent than most of the idiotic managers in these corporations and realizes that whatever succeeds will be with us for the next few decades and that separating such important projects splits the manpower and fragments our already small cummunity.
Why is this fragmentation a bad thing? To me it is what makes the open source community better than the alternatives. I have a choice of many different distros/torrent clients/browsers/desktop environments/gui toolkits/design philosophies/etc so why not display servers? You are making the assumption that for example there are 30 Mir developers and 30 Wayland devs and if Mir didn't exist we would have 60 wayland devs and everything would be done twice as fast, but that is not how it works. If the Mir developers didn't exist Canonical might put one developer on making sure there was compatibility between Wayland and Ubuntu and everyone else would be focusing on some other part of Ubuntu.Originally Posted by Redi44
I think the drama between the two groups is disappointing. Both of them seem to have some trouble with communication and that's the biggest problem I see in this situation.
It's pretty obvious Canonical is doing Mir separately for business reasons, and there's nothing wrong with that. There's also nothing wrong with commenters here believing that fragmentation is hurting linux.
Also Mir is more of a substitute for surfacefling, than anything else, which supports android drivers.
I don't think wayland could support A-drivers in the same way, or could be a pain to rework parts of it and then have upstream not integrate the patches, place them on hold or even refuse them.
IMO, with Mir canonical won't have any weird surprises or delays.
Last edited by madjr; 06-26-2013 at 11:30 PM.