3 ms·
I kind of disagree. GTK+ gets a lot of (sometimes deserved) flak for their API choices but Qt isn't all that different. They have plenty of weird legacy APIs, d
by jeroenhd 4y ago
I kind of disagree. GTK+ gets a lot of (sometimes deserved) flak for their API choices but Qt isn't all that different. They have plenty of weird legacy APIs, design choices, and restrictions on their API design so they can keep selling their paid products.
With GTK+ you get a Gitlab issue where everyone from GTK+ developers to /g/ users spout their opinions and then eventually the team and the developers take a decision that's probably going against at least half the comments in the thread.
With Qt you get "this is the API, live with it". I'd describe its API design method close(r) to the Windows API than any open source API I know of.
Sure, it creates a lot less drama, but at the cost of openness.
I'm not a fan of any Linux UI design toolkit, but I found GNOME Builder to be much more intuitive and working better out of the box than Qt Creator. GNOME's UI language may be... a choice, but Qt applications often feel like toy UIs or those fake operating systems you find in games without some pretty deliberate planning (and styling). With libadwaita being brought into GTK+ I think neither looks any good out of the box now, but the tooling for GNOME seems a lot better at least.
In terms of API and tooling support, I don't think any open projects come close to what Microsoft did with Visual Studio and C# back in 2005.
- sho_hn 4y ago> With Qt you get "this is the API, live with it". This is true often, but not always. Quite a bit of Qt APIs get created collaboratively on gerrit; I've had API changed based on my input. It's also possible to contribute APIs; I've done that, too. Some bigger new modules or API surface area is also moved through Qt Labs first before becoming part of the product, making for a longer feedback period. We've also had Qt folks actively attending events like Akademy to demo new WIP APIs and gather feedback and feature requests and engage in PoC ports of real software. There's also venues like the annual Qt Contributor Summit for larger discussions. You're right that this open approach is not the only channel for APIs into Qt, and in hybrid communities like his there's always some tension, and of course having to be a little "in the know" or engaged in the community means there's perhaps a higher barrier to entry in some ways. I respect not liking that and preferring if there's only a community-based channel. It's also worth pointing out that for the most part, Qt has a fairly healthy approach to low/mid/high level customizability and extensibility to its API. It has internalized this as one of the reasons for its success, even if it sadly fell a bit by the wayside during the early Qt Quick years. That means that "this is the API, live with it" is not really a straitjacket - you get to override, supplant, extend a lot.
- guerrilla 4y ago> With libadwaita being brought into GTK+ I think neither looks any good out of the box now, but the tooling for GNOME seems a lot better at least. Yeah, this is the part that hurts. So much work done on the backend and so many great apps, then to lock everything into that...
- zorr 4y agoWhat is the problem with libadwaita?
- guerrilla 4y agoIt's ugly (to some/many) and unthemable which is a huge problem when aesthetics are subjective and highly variable. The unthemability is intentional and intended to be permanent, which won't just apply to GNOME but all Gtk+ programs. So, an authoritarian disaster and big step backwards.
- zzo38computer 4y agoI dislike many things about GTK, although I have not tried to program using it so I cannot comment about the API (I have not programmed using Qt either). Qt is not that good either, in my opinion. I prefer Xaw, and I have done some programming using Xaw. (What I want is a compatibility library with the same API as GTK and Qt but does just calls other widget sets instead)