[Development] Basing Qt Creator Coding Style on C++ Core Guidelines?
Thiago Macieira
thiago.macieira at intel.com
Tue Nov 22 08:04:56 CET 2016
On terça-feira, 22 de novembro de 2016 05:59:24 PST Marco Bubke wrote:
> > I guess GTK maintainers suffer, specially with the last changes they
> > announced some time ago about breaking API/ABI (sorry, I don't remember
> > exactly which one) in some minor releases. Incindentally the first thing
> > we Qt maintainers though about those changes is how lucky we are to have
> > such a string-minded upstream that guarantess ABI during the life of a
> > major version.
>
> So GTK maintainers can do it. There are much more applications on my Linux
> Desktop so it is possible. And like Linus Torvalds has said, it is
> questionable to provide a package for every application on Earth. Flatpack
> is a much more reasonable choise for the developer and the user.
First of all, GTK maintainers haven't started doing their weird dance of ABI
breakage. We don't know if they'll actually go through with it and, if they
do, for how long they'll keep doing it. It's very likely that distributions
(aside from GTK-centric Fedora) will not keep the unstable versions updated,
so they'll get less testing. I find it highly likely the GTK developers abandon
this weird dance before or during GTK 5 because of the mess they created.
I don't agree on the philosophy of the flatpaks and similar because they're
based on a shifting foundation. Oh, it's ok to have a random app here and
there that I barely ever use not follow the system L&F -- for example, the
Intel Parallel Studio installer (a Qt 5.6 application). But the everyday
applications must be native.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
More information about the Development
mailing list