# JSTotD: Why async functions?

**URL:** <https://forum.kirupa.com/t/jstotd-why-async-functions/642184>\
**Category:** web dev\
**Created:** [March 23, 2020, 3:32am UTC](https://forum.kirupa.com/t/jstotd-why-async-functions/642184 "2020-03-23T03:32:42Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Vigus](https://yyz1.discourse-cdn.com/flex011/user_avatar/forum.kirupa.com/vigus/32/11089_2.png) [@Vigus](https://forum.kirupa.com/u/Vigus)\
**Post date:** [March 23, 2020, 3:32am UTC](https://forum.kirupa.com/t/jstotd-why-async-functions/642184/1 "2020-03-23T03:32:42Z")

</div>

Re: [Async Functions and await](http://forum.kirupa.com/t/javascript-tip-of-the-day/641803/44)

So the basic reason for introducing such functions are mainly an attempt to reduce the code size, nesting and hence the complexity? Just a better way to organise the code? Because they don’t seem to do anything new.  
I saw similar changes in coding methodology in Unity too while scripting with C#. It’s called IEnumerator, which is coupled with yield return. And that reduces the code which is otherwise difficult to read if replaced by event-listeners.

---

<div class="post-metadata">

**Author:** ![senocular](https://yyz1.discourse-cdn.com/flex011/user_avatar/forum.kirupa.com/senocular/32/7217_2.png) [@senocular](https://forum.kirupa.com/u/senocular)\
**Post date:** [June 8, 2020, 11:21pm UTC](https://forum.kirupa.com/t/jstotd-why-async-functions/642184/2 "2020-06-08T23:21:29Z")

</div>

2 posts were merged into an existing topic: [JS Tip of the Day: Async Functions and await](https://forum.kirupa.com/t/js-tip-of-the-day-async-functions-and-await/643147)

---

<div class="post-metadata">

**Author:** ![senocular](https://yyz1.discourse-cdn.com/flex011/user_avatar/forum.kirupa.com/senocular/32/7217_2.png) [@senocular](https://forum.kirupa.com/u/senocular)\
**Post date:** [June 8, 2020, 11:21pm UTC](https://forum.kirupa.com/t/jstotd-why-async-functions/642184/3 "2020-06-08T23:21:29Z")

</div>


