Originally posted by mdedetrich
View Post
Announcement
Collapse
No announcement yet.
GTK 4.0 Toolkit Officially Released
Collapse
X
-
Originally posted by mdedetrich View PostC++ is a terrible choice for a general purpose GUI library because the C++ ABI breaks all of the time.
Originally posted by mdedetrich View PostEven though C has its fair share of problems, one of its redeeming features is having an ultra stable ABI (talking decade, or even more here).
Comment
-
Originally posted by mdedetrich View PostIf you consider name mangling as part of the ABI (which you reasonably should) then it does break very often.
Originally posted by mdedetrich View PostThe matter of fact is, C++ is much more complex than C which makes it harder to provide a reasonably stable ABI (in practical terms).
Comment
-
Originally posted by 144Hz View Post[USER="68985"]
Of course Debian’s GNOME team is super fast but as a general rule your mind processing shouldn’t be slower than Debian packaging..
"Rust Bindings for the GTK+ 3 library"
I don't care about "modern" names at all. Consistency is more important to me. I think that is generally agreed upon by many projects (https://openports.se/x11/gtk+4). It will probably remain Gtk+ long after Gtk actually becomes obsolete and replaced with another software.Last edited by kpedersen; 17 December 2020, 08:04 AM.
Comment
-
Originally posted by zxy_thf View PostThe ABI problem is not only about the breakages, but also the incompatibilities.
One can compile a C library with GCC and link it with Clang, or vise versa, but this won't work for C++.
Comment
-
Originally posted by oleid View PostAnyway, huge pain points in GUI toolkits is multi threading. C++ won't help here. Sure, there are mutexes, however, the language won't help you to make sure everything is threadsafe.
Originally posted by oleid View PostI recall multithreading being a huge PITA in Qt.
Comment
Comment