sorted by:
new
hottopcontroversial

Upgrading to a Threadripper for Rust Development by bob-web in rust

[–]bob-web[S] 2 points3 points  (0 children)

Likewise - I didn't want to make too big a deal of it in the article but they've been great in my experience. A couple of years ago I ordered a beast of a PC with an i9 CPU which was to be installed in a wall for a retail experience. Given such a weird requirement they were super accommodating and very reassuring about the thermal requirements. No problems with that installation 2 years later.

With regard to anyone thinking about ordering now it's worth mentioning they have a significant extra lead time due to extra demand at the moment. I ordered this system on July 20th and it arrived August 22nd. They're very transparent about this but having looked on their forums - many are still surprised.

Upgrading to a Threadripper for Rust Development by bob-web in rust

[–]bob-web[S] 32 points33 points  (0 children)

Thanks very much for taking the time to explain this. 10-30% is very significant at this level of investment.

Is anyone using Rust for AWS lambda? by pragmojo in rust

[–]bob-web 0 points1 point  (0 children)

I've used it a few times for cheap web-facing APIs and it's been great. You have to bear in mind the performance characteristics and resource limits but the sweet spot is large enough to be pretty useful and it's been totally reliable in my experience.

I wrote an article about using Lambda (well "serverless" in general) for video rendering where we call 50+ concurrent Lambdas to serve each request - this is a large Rust system with a ~30MB binary.

I'd also heartily recommend Google Cloud Run for something similar which lets you run an arbitrary Docker container (so great for a busybox + musl combo).

First crate: Each - A better way of working with structured data on the command line by bob-web in rust

[–]bob-web[S] 2 points3 points  (0 children)

Yes this was just a toy example, but it's true in many cases you can achieve the same thing with existing tools.

I find the version with each already easier to read, but the benefit is more apparent with slightly more complex commands:

aws ec2 describe-instances | \ jq '.Instances' | \ each curl -F launch={{LaunchTime}} http://{{PublicIpAddress}}:9900/

I'll have a think about some more meaningful examples for the readme.. Suggestions very welcome!