Baz / Roadmap
Where Baz stands
Baz supports native Windows x64, Linux, and macOS. All three have passed Debug/ReleaseSafe verification, package checks, all 20 ported-example groups, and all 14 streaming groups. Windows also passed shard-handoff and console-shutdown cases. Baz remains experimental; these are correctness gates, not production qualification.
Implemented
The streaming App.
- Typed App, routes, and endpoint methods
- Raw query and form views; explicit codecs
- Flat multipart parsing
- Reserved response drafts and JSON
- Cookies, explicit expiry, and redirects
- Mustache templates with bounded rendering
- Streaming with a standard Zig writer
- Typed continuations: many streams, few workers
- Public middleware and typed request locals
- Reusable sessions with server expiry and revocation
- SSE encoding and bounded producer notifications
- A complete live-job application
- Caller std.Io and fixed worker services
- Native Windows x64, Linux, and macOS
Next API work
More ways to compose.
- Further response-copy reduction with explicit stream borrows
- Broader asynchronous service integration
Deferred / out of scope
Keep the scope honest.
- WebSockets: needs an upgrade lifecycle
- An owned std.Io provider and prototype: deferred
- TLS: out of scope
The framework reserves its own storage at startup. Application code and the caller’s I/O provider have separate resource responsibilities. Fixed workers do not provide arbitrary application isolation.
Follow the multi-session roadmap →