Honestly C# async/ await model is not that bad.

i mean, it IS syntactically identical to javascript’s way of doing it…

@fullstackchris I believe C# had it first?

@donuts does AJAX not count?

@wackOverflow did it have those keywords?

https://softwareengineering.stackexchange.com/...

Looks like
Haskell
F#
C#

@donuts looked over the Ajax spec and nope it doesn’t, and for that matter isn’t really comparable. All hail Haskell then.

@wackOverflow Ajax is quite different from async ;) and when it first came around it used callbacks or synchronous calls if you told it to.

Async await in js came much later, around 2017 and after n c# it came around 2011/2012 and haskell added the keyword around the same time.

https://softwareengineering.stackexchange.com/...

@Voxera the a in ajax stands for async(hronous)!

you said it as if someone complained about it at some point. It is pretty legit to me. And considering that the standards for language design and implementation are damn near identical, I would imagine that everyone is ok with it.

It's not that bad in my point of view.

When you say “honestly”, you let others know that other times you are not honest.

I agree. Async/await implementations make it easy to work with an asynchronous state. No more lasagna in the code.

I don't think I've ever seen anyone complain about it 🤔

@AlgoRythm I know ;). I used it before it was named ajax but remote scripting and also when you actually did send XML and not json.

And originally it was not even part of the browser but used a java applet for the actual callbacks to the server and a vbscript or jscript to map that to server side code.

But its still not the same as the async keyword.

Async builds on promises and that did not exist when ajax was created.