11 ms·
The sabotaging I speak of is in other things too; this is just the proximate example of their entire approach which began destructive through negligence, but se
by chrismorgan 4y ago
The sabotaging I speak of is in other things too; this is just the proximate example of their entire approach which began destructive through negligence, but seems to have become weaponised somewhere along the way so that although I doubt any involved intend malice, they have become complicit in organisational malice: because GNOME is not the only player in the space, but they’ve tried to take it over and are doing harm to everything else with their policies.
In this case: they’ve taken something that used to work across the board under X, and which is still used extensively, and for which there have been a number of well-reasoned pleas, and actively removed it by refusing to implement it under Wayland, although it should be fairly straightforward to do and is required for a parity that a great many apps and users desire and some apps need, and although not doing it forces apps that don’t (perhaps can’t) use GTK and don’t need client-side decorations to produce worse results. (And requiring GTK is nasty for non-GNOME apps anyway.)