3 ms·
GTK and Qt basically¹ churned their code once on this century. The other widget libraries didn't change at all. And at least Debian comes with the previous ver
by marcosdumay 4y ago
GTK and Qt basically¹ churned their code once on this century. The other widget libraries didn't change at all.
And at least Debian comes with the previous version of GTK, if you want to depend on it. What, of course, nobody does, because staying up to date is a matter of recompiling and changing a few function calls. (It doesn't have Qt3, probably because it's much harder to ship multiple Qt versions system-wide.) And, of course, you can always include your widgets with your code.
This is basically the amount of churning you get for any general application because of the glibc instability. That one is hard to circumvent, but there shouldn't be more of it on the future.
1 - Qt has had two incompatible changes, one of them removed almost nothing, GTK literally has had one. There is, of course the Qt6 thing, that breaks everything again, but I doubt people will migrate.
- hedora 4y agoYes, but gnome two and three cannot coexist on the same box, so distros like Mint ended up forking Debian to preserve access to the old gtk ecosystem. Later, gnome announced they were moving to a rolling release model that would routinely break backward compatibility. Since then, I've stopped paying attention, but noticed that QT utilities are slowly replacing all the (still maintained, but stalled, feature wise) gnome programs I used to use.
- jcelerier 4y agoOn a 500kloc Qt codebase I had maybe 4/5 files which needed changes following Qt5 -> Qt6, plus a couple of bugs that cropped up in the early versions. Plus most of the issues were in private API uses which are outside of the stability contract anyways. Now I know that I'm safe from breaking changes for at least 3/4 years until Qt7 ... Wouldn't call that churn haha.