# \[#36\] Zig Roadmap 2024 - Andrew Kelley

**URL:** <https://ziggit.dev/t/36-zig-roadmap-2024-andrew-kelley/3024>\
**Category:** Media\
**Created:** [January 27, 2024, 4:17pm UTC](https://ziggit.dev/t/36-zig-roadmap-2024-andrew-kelley/3024 "2024-01-27T16:17:32Z")\
**Posts on this page:** 1\
**Showing post:** 17

<div class="post-metadata">

**Author:** ![Sze](https://ziggit.dev/user_avatar/ziggit.dev/sze/32/496_2.png) [@Sze](https://ziggit.dev/u/Sze)\
**Post date:** [January 31, 2024, 1:42pm UTC](https://ziggit.dev/t/36-zig-roadmap-2024-andrew-kelley/3024/17 "2024-01-31T13:42:14Z")

</div>

## Question: Can we have a couple of words about async?

timestamp: [https://youtu.be/5eL\_LcxwwHg?t=1842](https://youtu.be/5eL_LcxwwHg?t=1842)

### Paraphrased:

Andrew explains that it currently isn’t practical, because there are a lot of difficult problems, that are in the way of a good implementation of async, these other things need to be addressed first.

### Summary

And I tried to transcribe the summary in the video:  
timestamp of [async/await summary](https://www.youtube.com/watch?v=5eL_LcxwwHg&t=2037s)

> Ultimately, I think it can be recovered, I think we can have async/await.  
> But it is just an extremely difficult technical problem to solve and I am not willing to solve it in a half-assed way.
> 
> I don’t wanna just check an async/await box, it’s gotta be good.
> 
> Let me do it on my own time, we will get there, but there is just multiple huge technical problems to solve, to make it actually good.

---

_[View the full topic](https://ziggit.dev/t/36-zig-roadmap-2024-andrew-kelley/3024)._
