Earlier quoted context omitted.
> [...] You're doing the same thing I was talking about earlier, manually reconfiguring every shortcut in every app and dealing with all the resulting bugs yourself. [...] Because key themes were just broken. OK so what is the ideal solution in your opinion? If key themes are broken, and having the ability to reconfigure a single key (for any single, or all apps) in a central place is also broken, then what isn't? Ha…
>OK so what is the ideal solution in your opinion? Cheeky answer: The ideal solution is a smartphone. It has no keyboard. You don't have to worry about keybindings at all anymore. Real answer: There isn't one. Once apps can do their own keyboard handling and make their own keybindings, any hope of making a clean solution goes out the window. It's hacks upon hacks from there on, because anything a new app does could p…
So let me recap:
1. You've said Gtk/GNOME relies on volunteer contributions;
2. GNOME removes (or refuses to implement, mutter#217) perfectly reasonable features that both regular and power users need/want/rely on, without providing alternatives (unless the plan is to get libadwaita eventually linked into the kernel);
3. You tell someone who shows interest in said features (outlining alternative designs, implementations, diving into some of the edge cases, and weighting their pros and cons), that if they like these features, they should use macOS instead.
Conclusion: GNOME drives away the same people who have the motivation and expertise to contribute to the platform. Self-sabotage.
Here's a hint: it works for Apple, because Apple produces a polished and highly desirable product. But even Apple caters to their professional audience. It works for suckless, because they're elitists and mostly irrelevant. But even suckless maintains an official repo of community patches.
How many active forks of KDE do we have out there?