What is JZ?
JZ (javascript zero) compiles JavaScript ahead of time to a plain .wasm module: no engine, no GC, no type annotations, auto-SIMD, byte-identical output.
Valid JZ is valid JS – drop the compile step and the same file keeps running.
| Good for | Not for |
|---|---|
| DSP, audio, synthesis | UI, DOM, frontend |
| Images, video, pixels | Network, hot I/O, serving |
| Simulation, physics, games | Dynamic objects, monkey-patching |
| Parsers, codecs, compression | Allocation-heavy, long-lived states |
| Scientific, numeric, edge ML | Security, cryptography, arbitrary-precision integers |
| Hashing, checksums, RNG | Tiny calls where the JS/WASM boundary dominates |
How do I use it?
import jz from 'jz'
const { exports } = jz`export const square = x => x * x`
exports.square(7) // 49Is it fast?
What is not supported?
Why no types?
JZ infers types from your code.
Why not AS, scriptc, Porffor, ...?
- AssemblyScript: TypeScript-ish.
- scriptc: fails to run benches.
- Porffor: nice but broad, not fast.
- Javy: QuickJS runtime in WASM.
- Perry: TypeScript → native apps.
Can it go native?
Can it compile itself?
Yes. 
Is it production ready?
Unstable yet, pre-1.0.0, but main contract gets stabilized soon.
