Originally posted by Siekacz
View Post
Canonical doesn't have the expertise to create this kind of standard. They will have to do way more work, and there's no way they'll get their project done before Wayland, because Wayland is way ahead of them. Canonical could easily just create their own Wayland compositor and still call it their own, add whatever extensions they need to suit their purposes, and it would benefit everyone because we'd all be using the same standard.
Mir is goal-driven, not community-driven, what makes Mir development much faster. They don't need to wait on agreement on the community side to make things work.
Mir will be fully reusable with other DE's. Obviously, it will be designed to work with Unity, but it doesn't mean that running KDE or whatever won't be possible. What is Wayland designed for? Nothing.
Leave a comment: