SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
It's a shame that one of the major players in the Linux world, with money to throw around, insists on doing stuff like this.. Why not just throw money and effort at Wayland, rather than duplicating effort to develop their own in-house version?
It's all about control. Canonical don't have complete control over decisions in Wayland land. This is just more NIH control-freakery like the Gnome v Unity thing - though in that case Gnome were doing some pretty stupid things so it was easier for them to justify it. In the case of Wayland, I don't think they can make a valid technical argument for going their own way.
With any luck, everyone else will ignore mir and it'll end up as a Ubuntu only irrelevance.
P.S. They've already revised their "Why not use Wayland?" section once after their fud claiming that Wayland was insecure was quickly disproven.
I think Canonical should just do it. No need to justify it beyond that it is theirs. No one from Google needed to justify Android's display server, so why should they? I don't have to use Ubuntu. They could succeed in being a standard if they do it right, so I'm not going to give an opinion when they are just starting out.
Now that said, I actually like Canonical better than Red Hat. At least Canonical rests on whether they made the right decision solely, and Red Hat has their people building fiefdoms and trying to force their 'solution' on everyone because they've already made the right decision.
I think Wayland can be a viable display server for Slackware, in a number of years from now. I don't think I'd be in a hurry--and no need to be, since we already have X. And that's the most favorable response for a major component replacement I have. There are components that I'd never want to come into Slackware listed earlier. I don't understand why there is a need to keep rewriting userspace anymore.
Distribution: OpenSUSE 13.2 64bit-Gnome on ASUS U52F
Posts: 1,444
Rep:
Quote:
Originally Posted by dugan
Based on the Arstechnica writeup, it sounds like Mir will be quite tightly coupled to Unity and thus pretty much irrelevant to us.
Unity is moving to QT so it will share technologies with KDE so if mir works better for Unity it should also works good for KDE. Keep in mind Xorg is really old and a replacement is overdue to adopt new technologies.
If it mir works I bet other distros will start using it so it is relevant to the rest.
It's all about control. Canonical don't have complete control over decisions in Wayland land. This is just more NIH control-freakery like the Gnome v Unity thing - though in that case Gnome were doing some pretty stupid things so it was easier for them to justify it. In the case of Wayland, I don't think they can make a valid technical argument for going their own way.
With any luck, everyone else will ignore mir and it'll end up as a Ubuntu only irrelevance.
P.S. They've already revised their "Why not use Wayland?" section once after their fud claiming that Wayland was insecure was quickly disproven.
I (and I am not alone with that) doubt that Canonical even has the ability to create a working display server, less so in the tight timeframe they have given themselves for that.
And that they do it because Wayland lacks support for something they need is nothing but blatant lies, they never have contributed anything to Wayland or even discussed their issues with the Wayland developers. This really is about control, nothing more.
Xorg is really old and a replacement is overdue to adopt new technologies.
Years ago nobody envied a supermarket cashier using a touch
screen. Some Big Monkey told us "Desktop machines are obsolete,
tablets are the future" and everybody jumped to "embrace the
future".
In my country we use to say "La culpa no es del chancho sino del
que le da de comer" that literally says "Don't blame the pig but
who feeds it". One example is what happened in systemd thread,
those complaining about systemd and about my hard wrapped text
(obviously mobile phone users) at the same time .
Choose a name for today's religion "out of the box", "use and
drop", "the easy way", "just do it". Or should we call it
"planned obsolescence"?:
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.