Hacker News Reader

Comment by saidajigumi | Hacker News Reader

Yes. Canonical clearly lays out the project motivations, including not choosing to use Wayland, on the Mir wiki page[1].

[1] https://wiki.ubuntu.com/MirSpec#Why_Not_Wayland_.2BAC8_Westo...

View on HN

from Wayland creator Kristian Høgsberg: " things they claim wayland/weston input can't be extended to support: "... adjusting and extending X's input model is difficult and supporting features like input event batching and compression, motion event prediction together with associated power-saving strategies or flexible synchronization schemes for aligning input event delivery and rendering operations is (too) complex." is already implemented and working in weston today..." https://plus.google.com/100409717163242445476/posts

(from other thread on Mir)

Saw someone post this log from #wayland on reddit. An cursory reading seems to indicate ubuntu folks don't fully understand wayland, and at the very least didn't even bother discussing their perceived gripes with the wayland team.

edit: forgot the link! http://pastebin.com/KjRm3be1

What worries me is fragmentation of drivers. It can be a very serious problem.

They'll probably use the same KMS and EGL drivers that Wayland and others use.

If that's the case - it would be good. But I'm not sure about it yet.

Yes, this is covered in the wiki page linked to in the email:

  https://wiki.ubuntu.com/MirSpec

Reply on news.ycombinator.com