Yeah, but that's a slightly different issue. C abi stability means you can use whatever off-the-shelf ffi your language supports.
That's not the point. The point is other languages don't have FFI for c++ because it doesn't have a stable/standard abi, so it's much harder to make bindings to qt than to gtk for most languages.
Version one might take a bit longer, but you don’t have to re-write the qt bindings every three months.
I’m all for ABI stability, but without API stability, it’s meaningless.
First of all Gtk doesn't require a rewrite every three months...
Secondly, at least for dynamic languages, you typically don't need to worry about wrapping Gtk's API, you just wrap GObject, and use introspection to dynamically generate classes.
That’s nice in theory, but hasn’t gtk stopped providing API compatibility between minor releases?