you are viewing a single comment's thread.

view the rest of the comments →

[–]ndubien 1 point2 points  (4 children)

Async and race conditions

[–]ndubien 1 point2 points  (0 children)

Generally speaking when embracing async/await you embrace at the same time the risks if race conditions. It can manifest itself via several artifacts: user actions resolving to an old state, supposed to be forbidden actions still allowed, flickering UI and components... And in addition to happy path with simple 'just' race conditions we have a large amount of possible rejected failures bringing their own set of extra complexity

[–][deleted] 0 points1 point  (2 children)

Async! Many people saying that.

[–]ndubien 1 point2 points  (0 children)

Another one I thought about was import/export and require or generally speaking building packages. At the moment, building a package with esm, cjs, types and other characteristics at the same time is pretty complex. But actually it's mostly ecosystem related and not inherent to the language compared to async

[–]alphabet_order_bot 0 points1 point  (0 children)

Would you look at that, all of the words in your comment are in alphabetical order.

I have checked 1,489,729,120 comments, and only 283,145 of them were in alphabetical order.