I think, one big reason why people are gladly implementing libraries in Rust is that they’re useful even outside the ecosystem.
In languages which need a runtime environment (Python, Java, JS, Go etc.), you’re locked into that ecosystem. Your code will only run inside of that runtime, meaning someone using another language can’t run your code.
Rust does not need a runtime and it can generate libraries in the format of C. Any mature programming language can call into C libraries.
Plus, Rust’s performance means it’s actually quite worthwhile for higher-level languages to call these libraries.
nous@programming.dev 1 year ago
One of rusts biggest issues ATM is a less mature eco system. Especially when compared to something as old as python. Rust does have a light stdlib compared to other languages as well and leans more heavily on its ecosystem to fill the gaps. But common things are already well established and mature and the whole ecosystem is coming along quite well.
Currently the biggest issues are the more fringe areas, like libraries for specific APIs or services or areas people have not quite covered yet. But these are fairly quickly lessening as people write libraries as they need them to fill the gaps. I would say its ecosystem is most there, at least enough for most projects now.
And IMO rust has some very nice ergonomics for some libraries - such as json de/serialization that just don’t/cannot exist in other languages.