2 ms·
One of primary reasons that Rust adoption has been stifled at an org I work with is that the cloud provider we use (GCP) doesn't support Rust with client librar
by ZeroCool2u 4y ago
One of primary reasons that Rust adoption has been stifled at an org I work with is that the cloud provider we use (GCP) doesn't support Rust with client libraries or SDK's. We know there are 3rd party providers, but they're not willing to go without GCP official support and I can't blame them.
- ekidd 4y agoHonestly, when we automate GCP from Rust, we use a thousand lines of hand-written client code and a normal HTTP client. Auth we do using a library. We've also tried the open source GCP client libraries, but they were huge didn't support async at the time. (Still, I'm much happier hand-rolling some HTTP wrappers than using the official Google Python bindings. Those pull in tons of fragile dependencies.)
- ZeroCool2u 4y agoInteresting, I was always pleasantly surprised at how few dependencies the GCP Python bindings pulled in. You are hand-rolling HTTP wrappers though, so I think we have slightly different perspectives :)