Odds are they’re doing the same thing only in theory. In practice, the picture changes - typically the KDE devs are far more willing to maintain old and marginal features and/or support benefiting only a small chunk of the userbase. While the GNOME devs are way more likely to ditch it, babble something about their design vision, then try to convince the user “ackshyually you don’t need it”.
(A major exception is perhaps accessibility, mentioned in the text. It isn’t just the Wayland devs worried about it, but also the KDE and GNOME devs. In this regard props to all three.)
Odds are they’re doing the same thing only in theory. In practice, the picture changes - typically the KDE devs are far more willing to maintain old and marginal features and/or support benefiting only a small chunk of the userbase. While the GNOME devs are way more likely to ditch it, babble something about their design vision, then try to convince the user “ackshyually you don’t need it”.
(A major exception is perhaps accessibility, mentioned in the text. It isn’t just the Wayland devs worried about it, but also the KDE and GNOME devs. In this regard props to all three.)