Getting started
Zryna is being built as a strict, JavaScript-friendly language with three direct output paths: JavaScript, WebAssembly, and native code. It is not ready for production use yet.
For installation, runnable examples, expected results, and common errors, follow Run your first Zryna programs. That compiler-owned walkthrough explains the exact toolchain, M1/M2 profile selection, fresh output names, and supported target/platform combinations.
Learn M3
Section titled “Learn M3”Your first M3 programs is the
compiler-owned beginner path for exact --profile data-ownership-v1. Follow setup, complete
sources, build/run, expected scalar output and safe create-only reruns. Try aggregates, String/Vec,
ownership, lexical borrows and Shared/Weak, with rejected programs and executable corrections.
The public M3 profile documents supported hosts, scalar-only public observations, typed traps, resource limits and rejected capabilities. The conformance evidence binds the authorities. Zryna remains experimental and not production-ready.
Earlier profiles remain available
Section titled “Earlier profiles remain available”Omitting --profile preserves M1. Exact --profile control-flow-v1 selects M2 scalar control flow
and relative modules. Independent manifests and fixed-oracle regression gates remain unchanged.
Use Run your first Zryna programs for M1/M2.
M3 does not add a public aggregate ABI, browser bindings, WASI, Components, Windows/macOS native execution, tracing collector, FFI or threads. This is not a general zero-runtime or GC-free guarantee for future profiles. Read the authenticated status for provenance.
Bounded M4 components and capabilities
Section titled “Bounded M4 components and capabilities”Read the fixed M4 support matrix and
conformance boundary before selecting a mode.
The static matrix defines twelve rows and records not-evaluated; it does not itself
authenticate execution, installation, signed release, deployment or milestone closure.
- Browser scalar component: checkout build, pinned Chrome fixture, no guest imports; synchronous deadlines are post-hoc.
- Command walkthrough: checkout or a fresh content-verified installation, pure/error results and one caller-private literal environment key.
- Finite status service and separately approved clock/status: checkout-only loopback listeners; listener approval never grants guest clock permission.
Use the command sources, status example and denied/granted clock example. Installed components/browser/server, existing immutable beta H1, other browsers/platforms, general WASI authority, signed release authentication and production admission remain excluded. M0–M3 keep their existing profiles, bounds and manifests. The publication gate and milestone closure remain recorded in Issue #402.