If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

Mir Gets Screencasting Improvements, Other Changes

03-12-2014, 05:10 AM

Phoronix: Mir Gets Screencasting Improvements, Other Changes

While the Mir display server isn't being relied upon by the desktop in Ubuntu 14.04 LTS, it is being used right now by Ubuntu Touch and Canonical developers are still working on its development in a steadfast manner for deployment in a future Ubuntu Linux release. Here's some of the latest commits to Mir...

Comment

Except that Wayland is an API and Mir is a compositor, which can add the Wayland API in the future.

No, Wayland is a protocol, Mir is the one that relies on an API. You can use Wayland libraries that expose an API to make it easier to access the protocol, but it is not required. Mir, on the other hand, requires you use an API, its protocol is not stable.

It may or may not be the case that Mir could implement the Wayland protocol, it depends on how different the underlying architectures are.

Why would Canonical use and contribute to KDE? They want their own unique experience which they can control.

There is no reason they couldn't have implemented Unity as a plasma workspace and gotten the exact same experience with less work. Or they could have relied on KDE Frameworks and implemented their own desktop on top of that (their Qt switch comes well after KDE announced its plans to modularize for Frameworks 5). Instead they are using Qt 5, but reinventing the wheel in many places where KDE already offers most or all of the functionality they want.

Comment

There is no reason they couldn't have implemented Unity as a plasma workspace and gotten the exact same experience with less work. Or they could have relied on KDE Frameworks and implemented their own desktop on top of that (their Qt switch comes well after KDE announced its plans to modularize for Frameworks 5). Instead they are using Qt 5, but reinventing the wheel in many places where KDE already offers most or all of the functionality they want.

So it's not okay for Canonical to "re-invent" the wheel, but it was okay for Apple & Microsoft or Google with ChromeOS?