3 ms·
> C# has had async, await and parallelism for years For Scala developers, there's Scala Async, which is exactly what C# "async" is, implemented as a library: h
by bad_user 12y ago
> C# has had async, await and parallelism for years
For Scala developers, there's Scala Async, which is exactly what C# "async" is, implemented as a library: https://github.com/scala/async https://github.com/scala/async - plus Scala's `Future[T]` has a better design than C#'s Task.
> node.js and libuv are taking over
And both suck in comparison with Java's NIO and the libraries that have been built on top of it.
> Low level threads in Java are so goddamned awful and unavoidable that it makes me want to pull my hair out
Low level concurrency primitives are necessary for building higher-level abstractions on top. For example I need low level concurrency primitives for implementing a Reactive Extensions (Rx) implementation that does back-pressure: https://github.com/alexandru/monifu/ https://github.com/alexandru/monifu/
> the people downvoting this have no idea what I'm talking about and don't know what coroutines are
You're assuming too much.
- deleted 12y ago[deleted]
- deleted 12y ago[deleted]
- Locke1689 12y agoplus Scala's `Future[T]` has a better design than C#'s Task Why? The one issue I have with Task is the aggravating SynchronizationContext/continueOnCapturedContext. ConfigureAwait(false) really should have been the default. Otherwise, my experience with both seems about equivalent.