

Just as an example, neither the C++ documentation nor its sagely bloggers have ever shown why it is a good fit for, say, systems programming. A really neat way of handling bit-level data is actually in Erlang’s bit syntax.
Erlang requires a runtime environment, which disqualifies it for situations where you don’t have a filesystem to load the runtime from, like developing a kernel or for microcontrollers.
Of the popular languages, your choices are virtually just C, C++ and Rust for that.
More towards your general question: Not needing a runtime environment also means you can use C, C++ and Rust for cross-language libraries. For example, SQLite and OpenSSL have just been implemented once in C, and then you simply have a thin wrapper for Java, Python etc…
If you are looking to build a library that can be used by as many devs as possible, that’s a selling point which is hard to ignore.


You picked out my one argument where you have a (weak) counterargument and then declare there’s no other arguments. Does not sound like you want to understand…