3 ms·

Please continue hacking on X if that's your fancy, I agree that the codebase is fine as far as legacy codebases go, the real problem is that the protocol itself

Please continue hacking on X if that's your fancy, I agree that the codebase is fine as far as legacy codebases go, the real problem is that the protocol itself has issues and that can't really be changed without breaking backwards compatibility or breaking ABI in xlib. Adding yet another security policy to the X server might fix some issues people have, it unfortunately won't fix all the other problems.

stelonix 6y ago
It is not impossible to add a new version of the protocol while maintaining backwards compatibility. Applications are Turing machines and there is no such a thing as "impossible". Having a bc path for old connection requests while implementing a new API is entirely possible. There's no abi breakage as I understand it, since it's a client-server model.