Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

A New AWS SDK for Rust

aws.amazon.com

Post reply on HN
Print view View original

51–60 of 62 posts

Re: A New AWS SDK for Rust

#51

Post by Xunjin »

hctaw wrote: post #30
cbb330 wrote: post #16

How often do the domains of systems programming and cloud administration intersect? 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.

Having a mostly statically linked executable handle this rather than some bastard child of virtual environments and docker images is a dream come true.

Shoutout to the Tools teams which develops cross, it's really amazing, did a project ago and had some problems to compiling static with rustls (OpenSSL really bugs with me, who knows why) do I tried Cross and felt in love, just works

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.

Re: A New AWS SDK for Rust

#52

Post by RideAndWave »

zokier wrote: post #11

> Just like our newer SDKs, AWS used the Smithy toolchain and service models to build AWS SDK for Rust This is pretty impressive. I haven't looked at the SDK in detail, but managing to produce ergonomic APIs (semi-)automatically based on some service models for language as complex as Rust seems like a major accomplishment. I have most experience with the Python library (boto3) which is bit weird at places, but the Py…

I think there is a trend for a set of tools which auto-generate stuff. It started back with web tools generating websites from WYSIWYG, now it is getting everywhere.

We build services and models using https://www.protoforce.io, which also auto-generates client and server side. Generally, it is impossible to generate good code using templates only, so it has to be transpiled.

I think from amazon's side it was coming sooner or later anyway, with the amount of APIs they have - it is inevitable. I just can't see how many teams you need to have to manage all of the client side code for many languages.

Re: A New AWS SDK for Rust

#53

Post by KptMarchewa »

closeparen wrote: post #36

When is it actually desirable to imperatively program your cloud provider rather than using something like Terraform? Obviously there are services meant to be consumed from application code, but the infrastructure provisioning stuff?

Even if I wanted to use real programming language for that, Pulumi seems to be better choice.

Re: A New AWS SDK for Rust

#54

Post by catlifeonmars »

closeparen wrote: post #36

When is it actually desirable to imperatively program your cloud provider rather than using something like Terraform? Obviously there are services meant to be consumed from application code, but the infrastructure provisioning stuff?

I have built several services that do dynamic infrastructure provisioning in response to API calls as part of the core functionality. This isn’t unusual.

Re: A New AWS SDK for Rust

#55

Post by warmwaffles »

dboreham wrote: post #19
warmwaffles wrote: post #13

Earlier quoted context omitted.

Honestly though, VSCode has been pretty good in this respect. Although I wouldn't use it to write Java or Kotlin, but for C/C++/Zig/D/Rust it's been good.

writing Scala here in VScode.

I've had mixed success with VSCode and JVM related stuff. Although the projects I was working on were using some really obscure Maven stuff and god forbid gradle.

Re: A New AWS SDK for Rust

#56

Post by jen20 »

closeparen wrote: post #36

When is it actually desirable to imperatively program your cloud provider rather than using something like Terraform? Obviously there are services meant to be consumed from application code, but the infrastructure provisioning stuff?

When implementing a Terraform provider, for one. At one point I had the scaffolding up to build providers in Rust (contributing to Tonic and Rusoto along the way) - many of the bugs in TF providers would be resolved by generics and type safety.

Re: A New AWS SDK for Rust

#58

Post by tonyhb »

KptMarchewa wrote: post #53
closeparen wrote: post #36

When is it actually desirable to imperatively program your cloud provider rather than using something like Terraform? Obviously there are services meant to be consumed from application code, but the infrastructure provisioning stuff?

Even if I wanted to use real programming language for that, Pulumi seems to be better choice.

It's not, trust me. Use the terraform CDK instead.

Re: A New AWS SDK for Rust

#59

Post by antihero »

skohan wrote: post #29
antihero wrote: post #24

Earlier quoted context omitted.

Shit man, as long as they do a better job than they did with Amplify.

Not holding my breath there...

Ugh. To anyone contemplating using Amplify I would say:

Rolling your own UI components and straight up using the amazon-cognito-identity-js library and wrapping the bits you need in promises, is far far far less of a headache than using Amplify, unless being tied to Webpack and dealing with disgracefully lazy types is your idea of fun.

Re: A New AWS SDK for Rust

#60

Post by skohan »

antihero wrote: post #59
skohan wrote: post #29

Earlier quoted context omitted.

Not holding my breath there...

Ugh. To anyone contemplating using Amplify I would say: Rolling your own UI components and straight up using the amazon-cognito-identity-js library and wrapping the bits you need in promises, is far far far less of a headache than using Amplify, unless being tied to Webpack and dealing with disgracefully lazy types is your idea of fun.

That's what we're doing actually. I get the impression that Amplify was designed more for vendor-lock-in than actually solving the problem in the best way
Post reply on HN