# State of UDP networking support?

**URL:** <https://ziggit.dev/t/state-of-udp-networking-support/14084>\
**Category:** Help\
**Tags:** standard-library, networking\
**Created:** [January 27, 2026, 3:28am UTC](https://ziggit.dev/t/state-of-udp-networking-support/14084 "2026-01-27T03:28:30Z")\
**Posts on this page:** 1\
**Showing post:** 3

<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:** [January 27, 2026, 6:13am UTC](https://ziggit.dev/t/state-of-udp-networking-support/14084/3 "2026-01-27T06:13:26Z")

</div>

> [@nairou](#):
>
> Also, it looks like the `zio` library is getting a lot of attention as an I/O alternative, and has network functionality built-in. Is this because support is still lacking in the standard library? Or is `zio` more like a difference of opinion on API design from Zig?

I’m the author, so I can answer this.

When I started, std was heavily lacking in networking. The networking capabilities it had were fine for the use case of the compiler, but any external project that was usable in production had their own networking layer.

I didn’t want to write another asynchronous networking layer for my application alone, so I invested time into zio. From the ground up it’s built with servers in mind.

You can already use zio with the `std.Io` APIs. As the interface matures, maybe it will become the only API. Even the native zio APIs are heavily based on `std.Io` to simplify the migration. Once 0.16 is released, the I’ll start shifting more into just an implementation of the interface.

But I believe the the architecture of zio is already better than the planned `std.Io.Evented` in terms of design for writing server applications, so the runtime will stay.

---

_[View the full topic](https://ziggit.dev/t/state-of-udp-networking-support/14084)._