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.

X applications will continue to run, but only in some kind of emulation inside Mir. So how well the graphics drivers drive Mir, and how well the frameworks/toolkits work under that emulation will be very essential. Even if not a single line of application code is Mir-specific.

Comment

X applications will continue to run, but only in some kind of emulation inside Mir. So how well the graphics drivers drive Mir, and how well the frameworks/toolkits work under that emulation will be very essential. Even if not a single line of application code is Mir-specific.

Not really... Both Mir And Wayland handle x-apps the same way. via XMir and XWayland respectively wherein each X-App gets its own private X-server, that it thinks is in control of the hardware and when it thinks its displaying the buffers its actually pushing them to Wayland or Mir surface and then Wayland or Mir handles the actual displaying
XMir and Xwayland are no more emulators than Wine and even THATS a bad example

Comment

X applications will continue to run, but only in some kind of emulation inside Mir. So how well the graphics drivers drive Mir, and how well the frameworks/toolkits work under that emulation will be very essential. Even if not a single line of application code is Mir-specific.

That's not true, and just goes to show that you don't really know what you're talking about.

Even if it were, that would be Ubuntu's problem to make everything work. Not Valve's. They need all sorts of legacy X applications, not just a single vendor.

Comment

X applications will continue to run, but only in some kind of emulation inside Mir. So how well the graphics drivers drive Mir, and how well the frameworks/toolkits work under that emulation will be very essential. Even if not a single line of application code is Mir-specific.

That's not true, and just goes to show that you don't really know what you're talking about..

Even if it were, that would be Ubuntu's problem to make everything work. Not Valve's. They need all sorts of legacy X applications, not just a single vendor.

The problem is Valve's too, because Ubuntu is their preferred distro. And by extension, it becomes AMD's and NVidia's problem to make Mir perform well on their hardware, or else Xmir won't perform well, and thus Steam may not perform well.

Comment

So any performance issues with Mir will possibly translate to performance issues in Xmir.
The problem is Valve's too, because Ubuntu is their preferred distro. And by extension, it becomes AMD's and NVidia's problem to make Mir perform well on their hardware, or else Xmir won't perform well, and thus Steam may not perform well.

The same way Canonical changed its mind respect Mir several times (fixed protocol, not fixed protocol, etc), Valve is free to change its mind when Mir is out there if they consider Mir unsuitable (or the need to support X greater than the need to support Mir, and supporting both is considered too much burden).

Comment

It is an easy problem for them to solve: change their preferred distro. The fact that they claim right now Ubuntu is the easiest to target, doesn't mean they are forced to stick with Ubuntu if it starts causing them trouble down the road.

Comment

It is an easy problem for them to solve: change their preferred distro. The fact that they claim right now Ubuntu is the easiest to target, doesn't mean they are forced to stick with Ubuntu if it starts causing them trouble down the road.

Valve may stick a different distro into their Steam box, that is true. However, Ubuntu and its derivatives have all but marginalized the other desktop distros. So any change in distro support is going to be a tough sell.
I give to you that not all Ubuntu derivatives are going to follow to Mir, so some uncertainty remains here.