golang's approach is anemic, so it's not an either/or situation. Take a look at Java's approach (Loom + Futures + Structured Concurrency). It allows you to be

golang's approach is anemic, so it's not an either/or situation. Take a look at Java's approach (Loom + Futures + Structured Concurrency). It allows you to be succinct yet avoid the explicit async/await approach.