GTK

“leaving a margin on every menu, so that menus with icons or checkboxes do not look inconsistent”

“Now GTK or libadwaita seem designed to resist themes and introduce constant breaking of selectors or widgets”

“Gtk was a reaction to qt having weird license issues, which it still does”

“or GTK2, where for e.g. a text editing page like a wiki, I have a toplevel App component”

“I really miss Gtk3/4 File->open dialogs having the ability to take pasted filepaths without erroring out.”

“The community is doing a great job with creating GTK4 native applications.”

“GTK/Adwaita themselves aren't terrible (particularly with CSS to tone down the acres of padding) but I still take issue with the quasi-mobile app direction”

“has a lot of room for improvement, but I've come around substantially on their direction”

“Classic GTK is (much) better (RSS on Linux): GTK2 14 MB GTK3 24 MB GTK4 98 MB”

“I see 20-30 MB with GTK3 which is about the size of my full-featured macOS AppKit apps”

“getting something to appear the way you want it to in GTK is worlds easier than doing so in CSS”

“I wouldn't consider it robust nor easy to use. But most importantly, it doesn't look good, especially on macOS.”

“have always been robust, stable, well documented, and easy to use”

“hidden behind an unaccessible configuration option, and now it's hopelessly broken in modern GTK version”

“it's not a good one because it overlaps whatever else is in the scroll area”

“And GTK has GI which allows to basically autogenerate bindings.”

“the GTK part isn't really an "accidental complexity" but a must have for me”

“newer toolkits like GTK, Tk, wxWidgets, DWM, Cocoa, etc are great at today”

“to me it (well, mainly Gnome) looks and feels like trying to copy macOS without understanding what makes it great”

“If you made an app in GTK 1 (which looks beautiful, by the way, compared to modern GTK), people won't be able to just install it”

“it is not supported anymore. you can't build or run GKT2 based apps on new systems without building the GTK2 libraries yourself.”

“A cross platform app which uses something like GTK or QT will be a massively better experience for your users”

“It's a very snappy and low resource usage toolkit aimed entirely at desktop computers.”

“They are already well supported on every other platform and can look very native”

“its developers don't help by completely rewriting things every few years and breaking all existing code”

“every Gnome or Gtk app I've tried appears to be working perfectly”

“For GUI it has really good bindings for the major frameworks QT,GTK”

“I've found the DX for GTK to be at least tolerable. Not fantastic, but I can at least look at a particular API”

“it will be dropped just like gtk2 when people just don't want to maintain it”

“the last release is stable and there's no technical reason to remove it”

“Maintaining three separate UI stacks (WinUI, SwiftUI, GTK/Qt) is dramatically more expensive and slower to iterate on”

“things like the gnome apps and gtk4 are more consistent than any windows app”

“Desktop programs performed better 20 years ago when everything was written in Win32, Qt, GTK and others”

“in practice there is no stable public "API" for the classses used inside an application”

“Vertically aligning a set of decimal numbers with the separator the same place would be challenging in GTK and Qt”

“GTK realized the sense in doing this when the development of GTK3 began”

“we've gone from GTK 2 to 4, X11 to Wayland, Qt 4 to 6, with compatibility breakages with each change”

“A lot of native toolkits are much more amenable to learning than the web.”

“It is a CADT program: every new version is a complete and incompatible implementation of the old version.”

“Having a framework that can be adaptable, like GTK, allows for padded, but IMO reasonably-sized touch targets.”