But if we worked on C (when I say C I really mean any language compiled to assembly instead of bytecode) libraries more we could also have a base that is solid enough for the 'likelihook of issues to decrease'. The difference would be more efficient applications because there is no intermediate layer.
GIMP is my go to, because it's huge and although they fuck up regularly and have so many bad points, they are cross platform and they were the first big cross platform thing in my experience.
GTK is pretty shitty, i've used it a few times and Qt has always seemed easier and cleaner somehow, but they both have issues. I didn't and will never call them perfect, but they are a start.
I can see your argument for "this is a strong compatibility layer that exists now" I kinda hate that, don't work with that layer work to make the tools we have better.
I have the same issue with my current workplace using "SwiftMailer" instead of some sendmail mechanism, when something bad happens (a developer spamming FakerEmails) I could have quickly crippled the mail without affecting the application. It would have been elegant and "the unix way".
But because they love all these newfangled libraries, instead of a simple application like sendmail, I ended up having to stop the whole stack and setup a mail relay in-case this happens again.
The thing I like most about Rust is the amount of time I spend thinking of the things that will go wrong, I literally have to handle them instead of going by my experience of previous fuck ups (I have a lot of experience with fucking up). I'm not sure it will take off for the same reason... developers mostly want quick and simple in my experience.