- 2 Posts
- 3 Comments
visor841@lemmy.worldto Linux@lemmy.ml•Why Wayland adoption to have official support in programs is so slow?0·1 year agoAlso XWayland has many limitations as X11 does.
If an app has only ever supported X11, then it probably doesn’t care about those limitations (the apps that do care probably already have a Wayland version). And if an app doesn’t care about the extra stuff Wayland has to offer, then there’s not really a reason to add the extra support burden of Wayland. As long as they work fine in XWayland, I think a lot of apps won’t switch over until X11 support starts dropping from their toolkit, and they’ll just go straight to Wayland-only.
visor841@lemmy.worldto Linux@lemmy.ml•Developer Explains Why Explicit Sync Will Finally Solve the NVIDIA/Wayland Issues0·1 year agowill not solve issues with compositors not having it
Many compositors already have patches for explicit sync which should get merged fairly quickly.
graphical libraries not having it
Both Vulkan and OpenGL have support for explicit sync
apps not supporting it
Apps don’t need to support it, they just need to use Vulkan and OpenGL, and they will handle it.
Wayland doesn’t implement sync of any kind, they probably meant to say “the Wayland stack”
Wayland has a protocol specifically for explicit sync, it’s as much a part of Wayland as pretty much anything else that’s part of Wayland.
Nvidia is not the only driver that needs to implement explicit sync.
Mesa has already merged explicit sync support.
Glad to see some work being done on Plasma Bigscreen, I recently discussed TV UIs a bit with a friend of mine who currently does a lot of their gaming on a TV and will probably switch that computer to Linux when Windows 10 support ends.