Post like these are why the Rust community is mocked.
C and C++ aren't over. They probably never will be. The correct answer is that the author chose two languages to support because it's their library. It is, indeed, strange a binding doesn't exist for two of the most popular languages on the planet. Not a big deal.
A quick perusal of both github repos and job listings shows that C and C++ are definitely not "over".
It’s over in the sense that new projects don’t get started in C++ unless they have huge dependencies on C++ libraries, like video games. And they shouldn't, it would be irresponsible.
Obviously, legacy code - and so the job market - will remain present for a while. Although it already pays less than other languages.
I'm pretty sure it's not. Maybe you wish it was, but it's not. C is still commonly used as a "lowest common denominator" language, and other languages often use bindings to native C libraries. This is still very common, and well supported in almost all modern languages (sometimes even completely embraced by some implementations, like cpython). Even Signal has official C bindings (libsignal-protocol-c).
To reiterate my point, one may hope that C goes away, but objectively, in the foreseeable future, it continues to be a backbone of most software.
Rusts ABI may as well not exist however. Rust can co-exist with C. Everything else that depends on C's ABI won't be able to play nicely with Rust without significant work from one side or the other.
