In TypeScript syntax

MetaScript is a systems programming language, designed as TypeScript superset — meaning all TypeScript you already write, now doing system-grade work. Fast backends, serverless with millisecond cold starts, CLI tools that ship as single binaries.

Reusing what's mature

MetaScript translates your TypeScript to existing backends — C, JavaScript, WebAssembly. Those backends have decades of work behind them, so MetaScript builds on top instead of replacing them. You write what you already know — the toolchains do the rest.

Familiar TypeScript in; native binaries, JavaScript, or WebAssembly out.

function max<T>(a: T, b: T): T {
  return a > b ? a : b;
}

console.log(max(3, 7));
console.log(max("abc", "xyz"));

// Monomorphized: one specialized fn per T
int32_t max__int32(int32_t a, int32_t b) {
  return a > b ? a : b;
}

msString max__string(msString a, msString b) {
  return a > b ? a : b;
}

// No vtable, no boxing — direct calls
msPrintln(msNumberToString(max__int32(3, 7)));
msPrintln(max__string(MS_STR("abc"), MS_STR("xyz")));

Extend either way

Where frontend and systems developers meet — two worlds sharing one language, innovating from both sides.

Native-tier performance

Same TypeScript source, native output. MetaScript lands in the native tier — alongside C and Rust — not the runtime tier with Node or Bun.

Why MetaScript?