"Wayland proxy is load balancer between Wayland compositor and Wayland client. It prevents Wayland client to be disconnected by Wayland compositor if Wayland client is bussy or under heavy load."
I'm laughing my ass off. Apparently, Wayland compositors will kill the client if it fails to read events quick enough. This might happen if the client software froze or... if you have a 1000hz mouse that generates too many events. And instead of fixing the compositor behaviour, Red Hat decided... to add a proxy that caches messages for the application to process.
These people are the reason "software engineering" is treated as an oxymoron.
@icon_of_computational_sin what's so uniquely fucked to me is that while Wayland weenies accurately assess X as being akin to a pile of hacks; within the next half-decade we will see this sort of design-sin recommitted and IDT these people will be as annoyed until/if or when they realise
@zardoz03 Wayland has already become a pile of hacks. The main problem is that it’s been designed by the same group of people who made Xorg a pile of hacks, representing the same culture and mindset. If you dare to look through Wayland protocol specs (https://wayland.app/protocols), the vast majority have Unstable or Staging or DE-specific statuses and may become broken or deprecated at any moment.
Add comment