> You're wrong here. Check http://www.x.org/wiki/IntelGraphicsDriver at least. But I wasn't asking where it works, I was asking why it works faster on the same hardware. Hint: because it uses hardware-specific optimisations for 2D rendering, impossible outside of the driver, impossible in Wayland.
Actually, running SNA on _Wayland_ is not only possible, but it works RIGHT NOW.
Posted Mar 20, 2013 17:14 UTC (Wed) by renox (subscriber, #23785)
[Link]
One point Cyberax :-)
I wonder why Serge is so hell bent in finding imaginary drawbacks of Wayland even though it's not difficult to find real "drawbacks" aka trade-off in Wayland.
The latest one I've read in Wayland mailing list: some weird screen have different subpixel ordering depending on the pixel position(!!), so as Wayland clients doesn't know where their window are going to be displayed, they cannot do subpixel aware rendering on these screen..
I hope that these kind of screen are rare, bleah.
LCA: The ways of Wayland
Posted Mar 20, 2013 17:23 UTC (Wed) by renox (subscriber, #23785)
[Link]
To be complete: someone has a plan to add an extension fix this, so this may change, sorry Serge ;-)
LCA: The ways of Wayland
Posted Mar 20, 2013 18:39 UTC (Wed) by chris.wilson (subscriber, #42619)
[Link]
Claiming that will be the same speed is stretching the truth by about a factor of 2.
LCA: The ways of Wayland
Posted Mar 20, 2013 18:48 UTC (Wed) by Cyberax (✭ supporter ✭, #52523)
[Link]
Well, yes. There's an additional roundtrip (from the X Server to the Wayland compositor). However, there are no reasons why it's not possible to do completely locally (perhaps using a better API like OpenVG).