Roadmap

What Nish has built and what is left, with one page per work package. A checked box is built and on main; an unchecked one is not. An item marked (open question) waits on a decision that has not been made, and one marked (deferred) is wanted but not scheduled. Each package's design and its reasons are in its design note on GitHub, linked from its page; the state is kept here, and a pull request that lands a stage ticks its box.

Milestones

  • M1, programs: fib, gcd and a string CLI build with nish --link, under 20 KB
  • M2, data: nbody with structs and arrays matches C's output bit for bit
  • M3, Rust parity: the benchmark table within 10% of Rust, wasm and N-API demos
  • M5, self-hosting: src/ compiles src/, and stage3 is byte-identical to stage2
  • M6, one compiler: stage0 deleted rather than frozen, first released in 0.7.0
  • M4, 1.0: a frozen language reference (open question). Nish stays on 0.x, and a breaking change moves the minor, until 1.0

Up next

In order. Each package's page says what its next stage is and where it is specified.

  1. WP49: async/await on the server, and the TechEmpower top: meet stage 6's gate.
  2. WP39: The HTTP server: a TechEmpower entry, then a general-purpose server: G7's one handler, the nish/net/http-server façade.
  3. WP43: The HTTP application layer: stage 3, static files.
  4. WP21: Packages: S4, the build cache.

Open questions

In progress and proposed

Work package State Done
WP21: Packages In progress 5 of 7
WP22: Arrow functions as the declaration form In progress 4 of 5
WP28: Compatibility mode In progress 5 of 13
WP33: The round trip to TypeScript In progress 7 of 9
WP37: The OS sandbox In progress 5 of 9
WP39: The HTTP server: a TechEmpower entry, then a general-purpose server In progress 22 of 29
WP43: The HTTP application layer In progress 3 of 7
WP48: 32-bit references for linked classes In progress 4 of 9
WP49: async/await on the server, and the TechEmpower top In progress 4 of 6
WP51: References to capture-free top-level functions In progress 3 of 4
WP64: Temporal — dates, times and time zones In progress 1 of 6
WP65: The surface a lexer port asked for Proposed 1 of 5
WP66: C libraries from their headers Proposed 0 of 7
WP54: async on wasm, with the page as the executor Proposed 0 of 4
WP56: Generators whose memory stays flat: a string builder, and a scope per file Proposed 0 of 6
WP57: Module-scoped names Proposed 0 of 3
WP59: The wasm arena in a second, unexported memory Proposed 0 of 4
WP60: Dynamic dispatch over interfaces Proposed 1 of 6
WP61: Typed JSON, constraints and coercion in one pass Proposed 0 of 3
WP62: Nish classes from a JSON Schema Proposed 0 of 5

Landed

Work package State Done
WP0: The Phase 0 validator Landed 1 of 1
WP1: Control flow Landed 1 of 1
WP2: Classes, interfaces, structs Landed 1 of 1
WP3: Strings Landed 1 of 1
WP4: Arrays Landed 1 of 1
WP5: Modules, entry point, linkage Landed 1 of 1
WP6: Memory: escape-analysed stack, arena scopes, T | null Landed 1 of 3
WP7: Runtime and intrinsics Landed 1 of 1
WP8: Interop: wasm, N-API, headers Landed 1 of 1
WP9: Optimisation and benchmarks Landed 1 of 1
WP10: CI, diagnostics, the code registry Landed 1 of 1
WP12: Release engineering Landed 1 of 1
WP13: Differential testing against Node Landed 1 of 2
WP14: Self-hosting Landed 1 of 1
WP15: Performance first Landed 1 of 1
WP16: Result<T, E> and the end of throw Landed 1 of 1
WP17: Result across the ABI Landed 1 of 1
WP18: Generics by monomorphisation Landed 2 of 6
WP19: Stage0 retirement Landed 1 of 2
WP20: Threads: the runtime half Landed 1 of 1
WP23: The language surface a corpus review asked for Landed 1 of 1
WP25: Remove inheritance, widen implements Landed 1 of 1
WP26: The standard library Landed 1 of 1
WP27: Calling C Landed 5 of 5
WP29: The thread surface Landed 5 of 8
WP30: Bytes across the interop boundary Landed 1 of 3
WP31: Ranged integers Landed 1 of 4
WP32: Map and Set Landed 2 of 2
WP34: The network stack Landed 24 of 24
WP35: The capability report Landed 1 of 1
WP36: The capability policy Landed 1 of 1
WP38: SIMD Landed 10 of 10
WP40: Dependency capabilities Landed 1 of 1
WP42: A multi-core server from pre-forked processes Landed 1 of 1
WP44: Streaming file reads Landed 4 of 4
WP45: Name resolution: a DNS stub resolver Landed 1 of 1
WP46: Memory for programs that do not exit: regions Landed 4 of 4
WP47: Shared work across cores: regions, atomics and rings Landed 1 of 2
WP50: A WebAssembly module a TypeScript page drives Landed 6 of 6
WP52: Fast rebuilds for nish run Landed 1 of 2
WP53: Buffers and handles across declare function Landed 1 of 1
WP55: An object graph a WebAssembly module keeps between calls Landed 1 of 1
WP58: A discriminated union as a generic's type argument Landed 1 of 1
WP63: io_uring direct descriptors for nish:net Landed 6 of 6
WP24: async/await Superseded 3 of 4

Not built

  • WP41, a 64×64→128 multiply: measured on Poly1305, 14% to 21% faster natively but 19% to 27% slower on wasm32, so it was declined.
  • WP48's first design, a whole-program 32-bit mode or an i32 pool: measured and declined on 2026-11-11; ports use a tree's first-child and next-sibling links instead, which took about half the memory. WP48 is reopened above for linked classes the compiler picks.

WP-P, the pipeline prep, landed without a note, and WP11, documentation, is folded into every package.