These benchmarks compare VibeScript executed via WebAssembly against
equivalent JavaScript implementations. Both run in the same browser,
on the same machine, with the same algorithms. The VibeScript path
goes through: source → parse → type-check → compile to bytecode →
VM execution. The JS path is native V8 JIT.
Ready.
Note: VibeScript is not designed to outperform JIT-compiled JavaScript.
It is a safe, capability-bounded, deterministic language. These benchmarks show the
overhead of the VibeScript pipeline (parse + check + compile + VM) relative to raw JS.
The bytecode VM is a stack-based interpreter — no JIT. For pre-compiled chunks
(encode → decode → run), the parse/check overhead is eliminated.