I might need to take a closer look at it at some point. I’ve never used anything that uses it, and I haven’t inspected it or grasped the scope of libadwaita, but most times I’ve heard anything about GTK 4, there have been major bad things—selection bias, to be sure, and perhaps confirmation bias, but it may indicate
something. The three examples that come to mind immediately:
• They severely damaged text rendering and initially didn’t even acknowledge it as a defect, dismissing the report: https://gitlab.gnome.org/GNOME/gtk/-/issues/3787. More recently there’s some movement on the issue, but the initial reaction was not a good look, at least.
• Someone said various bad things about libadwaita here on HN a couple of weeks ago: https://news.ycombinator.com/item?id=30027002.
• Of accessibility, they’ve completely redesigned it, in a way that is very convincingly better, or will be once it’s all finished including supporting tooling, but the impression I’ve received from a couple of communities where it’s come up a bit at times is that at least when they released GTK 4 and told people “start adopting it!”, GTK 4 apps were opaque to screen readers, because half the plumbing was missing. This impression could be false, and if there was any lack, hopefully it’s addressed by now.
I’m curious what the state of affairs is for approximating native look and feel on Windows. GTK+ 2 had a once-fairly-decent win32 theme that became fairly significantly out of date after Windows XP, but there were also some more recent themes that did parts better (and other parts worse). I’ve never seen a Windows theme for GTK+ 3 that is even halfway decent for look, and feel is a dead loss (e.g. menu keyboard behaviour and list box popup positioning and behaviour are both just painfully wrong).
If they’re serious about cross-platform, attempting to match Windows and macOS look and feel (and completely ignoring Linux, for a while) is where effort should be placed. I don’t know if they are.