async

Understanding ES2016 async/await keywords require you to understand all of that, plus ES2015 promises, ES2015 generators, and how they're all orchestrated together to implement async/await.

The site is just a bunch of text without any async loading.

Create action -> action[dispatch 'action pending' -> async action -> dispatch 'action complete with data'] -> stores.

In my experience, the toughest thing to grasp about Flux was how to handle async server actions.

Wouldn't new features from 3.5 like async/await have given people more incentives to switch had they been released earlier?

Despite the fact that those scripts have the 'async' tag, they still impact loading time.

Sure, when you get into async it might confuse young kids (or experienced programmers), but most beginner stuff won't need callbacks.

The biggest problem I see is locking as all the crap is async so you'd need some sort of locking and query ordering to maintain data consistency.

The only thing that matters in my opinion is generators and (in ES7), async/await.

In reflux, it was never clear to us whether certain async server operations should be handled in stores or in the actions.

As you said, I had to wrap a lot of Node.js libraries, and then wire them up with core.async.

Can you give me an example of when you used async in Python?

Personally, I'd rather see a bigger app than a TodoMVC implementation with a "correct" example of async server actions.

Go do this thing async so if you don't work out I don't have to waste resources on you." It also drives a perverse incentive on the part of the interviewing organization.

Async chat tools, file sharing, conference calls, video chats, etc.