Sadly Qt 5, due to the Qt Company pushing FOSS "freeloaders" on to bleeding edge and unstable versions of Qt 6[0], is becoming less and less viable for non-comm

Sadly Qt 5, due to the Qt Company pushing FOSS "freeloaders" on to bleeding edge and unstable versions of Qt 6[0], is becoming less and less viable for non-commercial, cross-platform app development. Arch Linux now compiles Qt from KDEs fork[1] The only ray of sunshine here is that, with Qt 5.15 being the last 5.x release, we may eventually see all distros shipping it instead of the horrible version fragmentation you see now (Ubuntu 20.04 LTS and CentOS Stream are still on 5.12, Debian 10 is on 5.11, RHEL 7 is on 5.9). The rift being created between Qt 5 and Qt 6, and the lack of any stability for FOSS with respect to upstream support for Qt 6, means we will likely see lots more fragmentation on the KDE/Qt side in years to come. Qt 5 will eventually end up like Qt 4, which has been dropped from Archs main repos[2], despite having over 500 packages in AUR depending on it[3]. Of course, depending on a single fork likely won't work either. The KDE fork is going to be naturally Linux focused, and probably won't care to tend to any Windows or macOS that arise. GTK+ on other platforms sucks, but at least on FOSS platforms it's not a mess. [0] https://www.theregister.com/2021/01/05/qt_lts_goes_commercial_only/ https://www.theregister.com/2021/01/05/qt_lts_goes_commercia... [1] https://github.com/archlinux/svntogit-packages/blob/packages/qt5-base/trunk/PKGBUILD#L31 https://github.com/archlinux/svntogit-packages/blob/packages... [2] https://lists.archlinux.org/pipermail/arch-dev-public/2019-April/029560.html https://lists.archlinux.org/pipermail/arch-dev-public/2019-A... [3] https://aur.archlinux.org/packages/qt4/ https://aur.archlinux.org/packages/qt4/