Users in this space also appreciate Rust's reliability properties. They say things like "It's never my Rust services that set off my pager, and that makes me happy."
Personally I think having a strong type system with an IDE that instantly tells you if the data is the right shape is very valuable when interacting with network interfaces.
In Python you either send the request at runtime and see what the server responds with, or you read the docs, both of which are at least 10x slower than an IDE telling you nearly instantly.
Rust's type system can represent null and polymorphic types quite well, both of which are quite common in JSON-like network interfaces.
Macros work well for code generation that is often used to convert a network api spec into code.
Of course you can do types and macros in Python, but neither are primary features of the language so are not as well supported.
People are writing web services or data products that would need to interact with cloud services. Object stores, SQL interaction, lambda/serverless, etc.
I'd think that people using this SDK for cloud administration would be in the minority, but it's just a hunch.
I worry about that.
I can see Rust being attractive for high-traffic network apps, based on the idea of requests-per-second not being amortized over GC pauses.
Seems relevant.
If you have problems using musl with some libs, give it a go, you gonna love it ;P
https://github.com/rust-embedded/cross
Edit: my dumbass english failed me, sorry.
I often see Rust used for microservices (where Go is often used), for which access to AWS is very nice to have.
I'm assuming that rust programs are primarily used in systems programming and that this SDK would be used for cloud administration but I could be wrong.
I see an obvious match with python and boto3 but not this.