Ubuntu's Mir Gets Delayed Again
jones_supa writes "Delays keep piling up for the Mir display server on the Ubuntu desktop. After already being postponed multiple times, Mir might not be enabled by default on the Ubuntu Linux desktop until the 16.04 LTS release — in two years time! This was the estimate by Mark Shuttleworth in a virtual Ubuntu Developer Summit. Using Mir, Mark says, will lead to supporting more hardware, obtaining better performance, and 'do some great things' with the technology. He expects some users will start using Mir on the desktop over the next year. Mir is already packaged as an experimental option, along with an experimental Unity 8 desktop session."
If Wayland is able to make decent ground before Mir is ready, there's still hope Ubuntu will drop the whole thing.
Version numbers don't mean a whole lot. Google Chrome hasn't changed much in 33 versions.
I've found (as a rule of thumb) that, when asking a grad student "How much time do you think you have left before you can write up your thesis?", if the answer is two or more years out then it really means "I don't know." The student honestly believes this answer, but in reality he/she doesn't know how much he/she doesn't know.
I'm starting to feel about the same with Mir and Canonical here. Shuttleworth is the tenured but aloof professor who casually coaxes his students (employees) toward completing milestones but without too much urgency. Money's not plentiful, but the professor has enough contacts and contracts to keep his lab going and give a stipend to his students. They put out a few papers (releases) each year, and each time the students think this grand project is "almost done"... only to discover that there's still more left to do.
There's tremendous value in this kind of exploratory research. I'm just not sure it makes sense to package it up for end users.
If I were Mark Shuttleworth's technical advisor, I'd suggest examining RedHat's Fedora model. Create a small group called Canonical Labs where stuff like Mir and Unity can flourish, with continuous releases and without the artificial constraint of a set release date. (If this makes the environment too lackadaisical and development isn't progressing fast enough, find some other way to instill discipline and/or motivation; don't make it the threat of moving alpha code to end-users.) When it's stabilized (no longer shuffling menus and window icons around, for example), then integrate it with the main Ubuntu branch. Something a bit more edgy and up-to-date than Debian Stable or RHEL, but not so much that it constantly upends your users.
You are really calling the people who have been using X for years "noobs"?
Using X does not mean understanding X. Additionally using X does not mean understanding how things have changed under the hood when there's been no visible change in the usability of the system.
Frankly a lot of X veterans who maybe once used X in a truly network transparent way think that just because their ability to send a window to another X system means it's still network transparent, which is utter rubbish. There's no modern distro which actually implements remote X in any other way than Wayland is proposing to do it, pixels scraping and sending it over the network.
Yet for some reason some people are still hung up on a feature which they think they use because frankly they don't understand anything, and the most vocal bunch seems to be the ones with the longest beards.