Rust is your "last language". It's good for writing Python native modules, PostgreSQL native modules, compiling to WASM, all using the same libraries you love and know already. That is a big deal for me.
Even if you mostly write Rust (or whatever), it’s still very useful to know other languages. Learning C will teach you how rust works under the hood, and teach you a lot about FFI systems everywhere. Learning javascript will be a massive help if you do web programming. I’m learning ML at the moment and python for that seems like a hard requirement. If you develop for Apple’s platforms, Swift is important to know. And so on.
And most languages just aren’t that hard to learn anyway. If you’re an experienced programmer, learning enough Go to be dangerous is a weekend project. It’s just not that much work.
The notion of "last language" that I used is, however, a bit different. It just meant that if you've implemented something in Rust, you won't need to rewrite in C or C++ due to presence of garbage collection or a need to integrate it as a library.
How so? Rust don't use C under the hood. (And even in ffi, you should just know the limitations of C to know what you can't do in FFI)
distributions are going to love your module! /s
There was a huge kerfuffle about it.
https://blog.yossarian.net/2021/02/28/Weird-architectures-we...
Terrible idea.
Everywhere else people ask for who's responsible when products don't match expectations, or are sold with faulty capabilities, unless the consumer protection laws of the country suck in protecting the citizens.