> GTK+ 3 stopped changing in drastic ways, which was well-received, and we are finally seeing applications moving from GTK+ 2.<p>It's almost as if devs care more about stable APIs than about endless churn for minor features!
I still really prefer GTK2 apps. The GTK3 file picker is awful, and I'm generally not a fan of apps that use the new fancy window borders like gedit.<p>I'm glad Mate is around to keep maintaining gtk2/gnome2.
As much as I always like GTK2 as a solid workhorse, and GTK3 (although unstable) was adding actual improvements, I lost a lot of faith in the GTK team with their original hare-brained versioning scheme for GTK4. When they recanted that plan and announced that GTK 3.22 would be The Stable Version, I felt a bit better, and honestly it's been pretty great so far.<p>Going back on that promise and saying that GTK 3.22 isn't actually The Stable Version after all feels a bit like a betrayal... but on the other hand, if gdk_window_move_to_rect() is the function I'm thinking of, all is forgiven.<p>I was trying to create a custom popup the other day and (thanks to limitations in the GDK API) it wasn't possible under Wayland. Trying to dig into why, I found out that GDK had an API that did exactly what I wanted, which I couldn't use because it was internal and unstable. Assuming that API is gdk_window_move_to_rect(), this is the best news I've heard all day.
For the applications I use, gtk3 did not add any significant improvement over gtk2. Often it was the opposite (goodbye menubars anyone?). It seemed like all my dank gtk themes broke every time there was a minor version bump.