3 ms·
Another obsolete "fact" about Wayland which hasn't been true since 2015. Which is all the anti-Wayland propegandists seem to be able to come up with. This was
by ddevault 6y ago
Another obsolete "fact" about Wayland which hasn't been true since 2015. Which is all the anti-Wayland propegandists seem to be able to come up with.
This was addressed by the linux-dmabuf protocol extension (which also works on *BSD, despite the name). The mesa route has been deprecated for years.
- ywei3410 6y agoI do believe that the parent comment was unfair; it is possible to implement a compositor without libwayland — but I do think that there is some truth in that the C structures are the de-facto protocol from the client-side. For example graphics drivers seem to expect wl_display and wl_surface [1] rather than, say expecting the object id. It’s not as though this is different under X though and isn’t a criticism of Wayland. [1] https://www.khronos.org/registry/vulkan/specs/1.2-extensions/man/html/VkWaylandSurfaceCreateInfoKHR.html https://www.khronos.org/registry/vulkan/specs/1.2-extensions...
- gpm 6y ago> isn’t a criticism of Wayland. Indeed, my comment is merely observing that wayland is both a protocol and a code base for all practical purposes, I'm trying to leave the criticism to other people ;)
- deleted 6y ago[deleted]