# Future prospects of Web Development with Zig?

**URL:** <https://ziggit.dev/t/future-prospects-of-web-development-with-zig/12917>\
**Category:** Brainstorming\
**Created:** [November 8, 2025, 1:46am UTC](https://ziggit.dev/t/future-prospects-of-web-development-with-zig/12917 "2025-11-08T01:46:53Z")\
**Posts on this page:** 1\
**Showing post:** 6

<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:** [November 8, 2025, 11:13am UTC](https://ziggit.dev/t/future-prospects-of-web-development-with-zig/12917/6 "2025-11-08T11:13:35Z")

</div>

> [@castholm](#):
>
> I believe the core team has said in the past that as far as HTTP client/server stuff is concerned, std will only provide the bare minimum necessary to serve the needs of the Zig compiler/toolchain itself.

Maybe this changed over time, this seems to indicate otherwise? I guess it depends on what is meant by bare minimum:

> [@Is std.http insecure?](https://ziggit.dev/t/is-std-http-insecure/11314/2):
>
> I think if a project wants to make such claims, it should link to open issues. I don’t know when this text was created, but here’s a brief timeline of std.http: Initial version of some random http APIs contributed I deleted most of it because I didn’t like it Initial version of http.Client and http.Server contributed I didn’t like either one. I rewrote Server but didn’t have time to rewrite Client yet Now I am [rewriting all of std.http](https://github.com/ziglang/zig/compare/master...http) Once I’m done, I’ll be happy to take responsibility for …

---

_[View the full topic](https://ziggit.dev/t/future-prospects-of-web-development-with-zig/12917)._