The plan

Where Zhex goes next.

Build a readable language from small, composable words. The Go interpreter lets us try the syntax and settle behavior before choosing a compiled implementation.

Next

Make it useful day to day.

Grow the language's reach: a dedicated domain and funding. This is the proposed order; each step needs working examples and tests.

  • Standard library: the researched inventory ships — 121 registered words; what remains is small and triaged.
    • The proposals and dependency order live in docs/standard-library-plan.md (#30).
    • Open gap tickets in the Inbox: #159 bitwise and stack words, #168 the 2024 day 24 part-2 solver analysis.
  • WebAssembly: the A3 WASI runner runs a compiled module under a standalone wasm runtime.
    • file.* words work against one preopened directory.
    • It compiles today but stays runtime-untested; docs/wasm-plan.md tracks it open.
    • Compiled wasm builds use 64-bit Ints by design — WebAssembly has no wider integer type, and wider values refuse with a named limit (#178 ruled the boundary final); the native Go target keeps the interpreter's full 128-bit width (#185).
  • Domain: buy a dedicated domain for the language and point it at the published site.
  • Funding: enable GitHub Sponsors or Open Collective and pursue the researched channels (#26).
    • A sponsor section on the site.
    • The grant and visibility channels from the funding research.

Future

Room to grow.

These are directions to explore. Their order and implementation remain open, and there are no delivery dates yet.

  • Rich values: generic records and words, and user-defined error types with readable operations and formatting.
  • Application libraries: grow through small CLI, HTML-processing, web-server, game, and database experiments.
  • Development tools: formatting, language-server support, and published editor packages as the syntax settles.
  • Development insight: record-and-replay runs, debug-adapter support, and agent tools, so people and AI agents can see and debug what a program is doing (see docs/diagnostics-plan.md).
  • Module growth: exposure lists, import renames, subfolder paths, and computed module constants, composing on the simple use-and-underscore design when each earns its place.

Follow the project board ↗ · View the roadmap source · Try the current examples →