Hacker News new | ask | show | jobs
by xedrac 1652 days ago
> if I'm going to write a worker that will read from a queue, do a transformation and write to a few more queues/services upon completion, Go just works and the turn around time is far better than Rust.

Since the inception of async/await in Rust, it is incredibly quick to whip something like that up. The slowest part might even be the time it takes to compile. Maybe that's what you were referring to?

1 comments

The way Go does it is easier to reason with, channels and goroutines are really easy to explain to anyone.
That does sound a lot easier than Rust's channels and tasks...