3 ms·
In 12 years they probably could have improved X a lot. But the impression I always got (years ago when this was a bigger topic) is it likely would have broken b
by MBCook 4y ago
In 12 years they probably could have improved X a lot. But the impression I always got (years ago when this was a bigger topic) is it likely would have broken backwards comparability to do right. And if it’s not compatible, is it still X? And would the Wayland haters/holdouts accept it?
IDK. I understand the direction they decided to take.
- noobermin 4y agoThe issue with screen recording is not due to backwards compatibility
- imachine1980_ 4y agoi try to learn x11, is hell, i realy try im tech savvy but god sake. is this problem difficult hell yea, but heavens x11 makes 10x more complex that should be.
- mbreese 4y agoI mean, when your default use-case includes remote rendering of a GUI to clients, you're going to end up with a complex protocol. In the era of heavy servers and thin clients, it makes a lot of sense. But when most (every?) computer includes some kind of GPU, local rendering makes the most sense -- especially when that's how your primary competitors work. I don't know enough about Wayland vs X11 to make an informed statement, but I do appreciate that Wayland explicitly didn't try to include remote rendering. Let's just leave that up to other protocols (VNC/RDP/etc...). Now if we can just get one of those protocols to work on an individual application/window basis as opposed to the whole desktop.
- simcop2387 4y agoThat would be waypipe, https://gitlab.freedesktop.org/mstoeckl/waypipe#:~:text=waypipe%20is%20a%20proxy%20for,%2DX%20%5B1%5D%20feasible https://gitlab.freedesktop.org/mstoeckl/waypipe#:~:text=wayp....