[vrotaru]

There was no real reason to rush the transition to GTK3, but it was done anyway.

GTK3 with its half-assed support of CSS for theming is just just bad, and slow (especially on Macs)

And they continued to change GTK3 API after 3.0, which did not exactly help

[vetinari]

> There was no real reason to rush the transition to GTK3, but it was done anyway.

If anything, Linux libraries move too slow. Meanwhile, while seeking perfection, the world around them uses the older releases, with all the downsides it entails, so they cannot wait until it is perfect.

> GTK3 with its half-assed support of CSS for theming is just just bad, and slow (especially on Macs)

Still much faster than Cocoa on Linux... What Cocoa on Linux? Exactly. Availability of Gtk on a Mac has 0 impact on how many Linux app will decide to use it.

> And they continued to change GTK3 API after 3.0, which did not exactly help

They added (and yes, deprecated APIs). Nothing that would affect existing applications. Themes were never part of the API and there was a warning, that it is going to change. If someone has to find the hard way, so be it.

[phkahler]

>> Availability of Gtk on a Mac has 0 impact on how many Linux app will decide to use it.

I sometimes consider using GTK as a cross-platform GUI vs what we do today (a small wrapper over Windows, macOS, and GTK) so we can have some nice things - like resizable text and SVG icons. Not supporting macOS would mean not using GTK for that. At the moment, no static linking means no GTK for that too because we ship a single binary for Windows and I don't want to deal with an installer.