Earlier quoted context omitted.
I disagree and think a clean break was the way to go. X had acquired a whole lot of legacy baggage and compatibility with that should be provided by a separate piece of code. Wayland should have been a completely new thing built with the lessons learned from X but vastly simplified for how modern display systems are actually used. Unfortunately it was built with no intent to handle many of the common use cases X alre…
I love how people say that an unified method of taking screenshots, screen streaming, screen recording and performance in general is legacy baggage.
Victims of this mimetic disease have caught on to the idea that 80% of usage needs 20% of the features.
This might well be true in a literal sense, but it ignores that 99% of the users need one or two items from the remaining 80% of the features and its just a different one or two items for each user.
The result is something that isn't completely functional for all but a tiny portion of the user base. :( Workarounds exist to expand that somewhat, though they're often extremely poorly maintained.
For example, I had a gnome3 using system that suddenly started insta-crashing anytime a GTK dialog was opened on it. I eventually had to blow away all its gconf to recover it.
It turned out that at some point someone decided that 300% and 400% scaling had no purpose and caused issues because in some cases they messed up UI layout. They removed them and the removal was just shipped along with security & bugfix updates in fedora. The way it was removed caused instant crashing for people that previously had them enabled!
I'm fixed now, though with the display at 200% I have difficulty reading it (It's a 4k TV that I need to read from a long distance away) ... but since I can't use gtk interface stuff on it at all now I guess I won't be opening any bugs on minor layout issues that might be caused by increased scaling. PROBLEM SOLVED :(