We know it's a deliberate choice. It's just wrong.
>This decision affords Wayland compositors a greater deal of flexibility — windows could be shown in several places at once, arranged in the 3D space of a VR scene, or presented in any other novel way. Wayland is designed to be generic and widely applicable to many devices and form factors.
Do ANY of these other features work? Furthermore, all our applications are built basically as 2D grids of pixels. What click position do you get if you render the same window in some "novel" way like in two places at once? I don't especially care if any of their space-age bullshit works. It NEEDS to work for the apps we have, which are just pixel arrays. Many users have been ranting about this issue for years and all we get in response from Wayland wackos is basically "live with it!" Nobody has realized any actual benefits in functionality from switching to Wayland. Maybe some graphics nerds with weird monitor setups are geeking out about fractional pixel coordinates and multiple refresh rates. The rest of us are just dealing with issues for no benefit.
> Maybe some graphics nerds with weird monitor setups are geeking out about fractional pixel coordinates and multiple refresh rates.
They're complaining too because Wayland upscales everything (quadrupling the number of pixels and trashing performance) in order to downscale it for fractional scaling.
> They're complaining too because Wayland upscales everything (quadrupling the number of pixels and trashing performance) in order to downscale it for fractional scaling.
Only once ? They could do this 3 times. For smoothness. /s
>This decision affords Wayland compositors a greater deal of flexibility — windows could be shown in several places at once, arranged in the 3D space of a VR scene, or presented in any other novel way. Wayland is designed to be generic and widely applicable to many devices and form factors.
Do ANY of these other features work? Furthermore, all our applications are built basically as 2D grids of pixels. What click position do you get if you render the same window in some "novel" way like in two places at once? I don't especially care if any of their space-age bullshit works. It NEEDS to work for the apps we have, which are just pixel arrays. Many users have been ranting about this issue for years and all we get in response from Wayland wackos is basically "live with it!" Nobody has realized any actual benefits in functionality from switching to Wayland. Maybe some graphics nerds with weird monitor setups are geeking out about fractional pixel coordinates and multiple refresh rates. The rest of us are just dealing with issues for no benefit.