> Think chromium-quality software quality [...] There's an irony somewhere in there that Chromium is a descendant of KHTML, KDE's rendering engine, which becam

> Think chromium-quality software quality [...] There's an irony somewhere in there that Chromium is a descendant of KHTML, KDE's rendering engine, which became WebKit and was originally written using Qt. And Google and Apple's contributions were regularly derided for being relatively low quality. Qt and KDE have always had a lot of cross-contribution, so KDE (its libraries, for example) is a good place to start: https://github.com/KDE/kdelibs https://github.com/KDE/kdelibs There's also this old, but still relevant, article on designing Qt-style APIs (which had a big impact on me personally): https://doc.qt.io/archives/qq/qq13-apis.html https://doc.qt.io/archives/qq/qq13-apis.html