# Zio - async I/O framework

**URL:** <https://ziggit.dev/t/zio-async-i-o-framework/12213>\
**Category:** Showcase\
**Tags:** networking, llm, async\
**Created:** [September 26, 2025, 8:18am UTC](https://ziggit.dev/t/zio-async-i-o-framework/12213 "2025-09-26T08:18:54Z")\
**Posts on this page:** 1\
**Showing post:** 115

<div class="post-metadata">

**Author:** ![lalinsky](https://ziggit.dev/user_avatar/ziggit.dev/lalinsky/32/3720_2.png) [@lalinsky](https://ziggit.dev/u/lalinsky)\
**Post date:** [May 12, 2026, 4:59pm UTC](https://ziggit.dev/t/zio-async-i-o-framework/12213/115 "2026-05-12T16:59:01Z")

</div>

> [@Zig Devlog high\_voltage io\_uring and Grand Central Dispatch std.Io implementations landed](https://ziggit.dev/t/zig-devlog-io-uring-and-grand-central-dispatch-std-io-implementations-landed/14315/3):
>
> I was just checking the code and I can’t tell if I’m seeing this right. Is it really allocating 60MiB stacks? slight_smile

We had a drama some months ago in this thread, where Andrew was saying how I’ll be fragmenting the ecosystem if I depend on overcommit in zio, so I actually implemented stack growth after that. And then I saw this. Who is fragmenting the ecosystem now? 🙂

I’m sorry, I’ll stop with the negative comments, but this one is too much for me to hold.

---

_[View the full topic](https://ziggit.dev/t/zio-async-i-o-framework/12213)._