3 ms·
Having had to migrate a very simple project from GTK2 to GTK3, I don't think it's all that weird. The migration was utterly difficult, in the areas that hit me
by onli 2y ago
Having had to migrate a very simple project from GTK2 to GTK3, I don't think it's all that weird. The migration was utterly difficult, in the areas that hit me seemingly no effort was made to give proper migration paths. Only with some later published documentation (+ help from chatgpt) was it possible to restore some functionality later, after the initial migration. Finally that even meant calling the xlib directly.
And note that the software used wxWidgets, so most of the changes were encapsulated there. Only a very small part of GDK/GTK was used directly, with wnck already used as a helper layer (but the functionality in question broke there as well).
So even if GTK came from GIMP, if the later development in GTK was not made specifically for and by the GIMP project, the migration must have been a nightmare. Especially in a project that had so many other things to worry about, non-destructive editing alone.
And to repeat such a migration now again for GTK4 will not be very enticing.
- mid-kid 2y agoFrom what I've heard surrounding this, GTK3 to GTK4 isn't as big of a jump as GTK2 to GTK3 was. The GTK3 port was finished first because there was already work in place for that, but we can expect a GTK4 port to be faster. That said, I haven't seen many apps that aren't specifically GNOME apps start using GTK4 in the first place, and as such I'm currently not using any GTK4 applications. I expect it to take a while before more things move to GTK4.