On Saturday, 16 June 2018 at 08:39:07 UTC, Dmitry Olshansky wrote:
On Friday, 15 June 2018 at 23:04:40 UTC, Sjoerd Nijboer wrote:
For someone coming from a C# background there is some
seemingly simple syntactic sugar missing from D.
T* he `async` & `await` keyword from C# make proactor pattern
async code extremely easy to reason about.
God please no. Look at Go’s popularity because of dead simple
go routines and “async i/o is transparent and looks blocking
but ain’t so”. We have at least vibe.d for that and possibly
more. Also see Java doing fibers recently, and Kotlin did them
just a year or so back. People love fibers and mostly dislike
Futers/explicit async, and plain callbacks are obvious last
resort that nobody likes.
async/await make asynchronous code in C# and JavaScript look
clean and easy to wrap ones head around it. Solution to aka.
callback hell. If popularity is what you're looking at, it
JavaScript not Go. And async/await is all over the place...it
more that a syntactic sugar, it a pattern.
‘async’ is viral keywords that poorly scales, I worked on Dart
core team and even they admitted this problem is not solved
well.
Doesn't scales for what?
Try C# or JavaScript and experience the true power of async/await.
