News for hackers. Stuff that matters.
Re:I'm not feeling the async pressure by alpb on Thursday January 02, 2020 @01:19AM (#21933382)
How's it different than Go's context.Done() channel? Similarly it bubbles up everywhere the context is passed immediately, letting you terminate concurrent routines.

I've used both .NET async/await (4 years ago) and Go ever since. The semantics and feel is nearly the same, the look is different.

Re:I'm not feeling the async pressure by egeozcan on Thursday January 02, 2020 @03:38AM (#21933822)
IMHO, being able to throw the error and it moving magically up the async stack (aka try/catch) makes it easier to get started while go makes it easier to maintain by forcing you to design a system around channels. This opinion is coming from a decade of .NET but just a few months of go experience so it's very skewed.