Re: GTK3 and the Gnome team........
> Quote: "...restores support for GTK3..."
You are missing *THE* key word.
«
It restores support for Gtk3 _themes_
»
That's all.
It does not turn Gtk4 into anything Gtk3 compatible.
I do not program myself. When I used to dabble, I didn't like C. I wrote one vaguely useful (to me) C code module, a tiny run-length-encoding compressor/decompressor for monochrome images. I decided I didn't like C and never really touched it again.
But what I have read around the edge of Gtk4, it drops many things that are core to industry-standard UIs.
As I've said in the article, I find many GNOME communications to be obscurantist bafflegab, and the GNOME team _does not like it_ when I say so. Several prominent GNOME team members blocked me on Twitter, back when Twitter mattered, including Emanuele Bassi, who was the author of the answer where that mealy-mouthed definition, "the building blocks of GNOME apps", came from. (I may have misspelled that.)
As a small example, Gtk4 does not support menu bars any more, because GNOME 4x apps don't have menu bars -- they have hamburger menus instead. (Use a screenreader, or want to get a quick overview of functionality in words? Yeah, fsck you.)
I think true title bars are on the way out too. Famously for about a decade it could not show file thumbnails in the Open/Save boxes. There are many examples.
Gtk1 is still alive and I've been talking with the maintainer recently. Gtk2 is still sort of alive and things in wide use are built in it.
Gtk3 is currently the dominant version. As you say, even GIMP 3, _the app for which Gtk was designed and built_, uses Gtk3.
I think it may turn out that most of the industry stays with Gtk3 and GNOME goes off on its own way with Gtk4 and the rumoured Wayland-only Gtk5.
As for the rest of your comment: well, yes, personally, I tend to agree.