Perry vs the alternatives

How Perry compares to other ways of shipping TypeScript: runtimes, compilers, and cross-platform UI frameworks. Honest, sourced, with measured numbers where they exist.

TypeScript runtime

Perry vs Bun

Both can produce a single executable, but the contents differ. Bun bundles the application with a copy of the Bun runtime. Perry compiles supported code to native machine code and statically links its own runtime and GC without a JavaScript engine by default.

TypeScript runtime

Perry vs Deno

Deno compile produces a standalone executable by bundling a slimmed-down Deno runtime with the program. Perry compiles supported code through LLVM and does not include a JavaScript engine by default, while statically linking its own runtime and GC.

TS-to-native compiler

Perry vs Static Hermes

Perry and Static Hermes both explore ahead-of-time JavaScript/TypeScript compilation, but they have different runtimes, toolchains, target goals, and maturity. Static Hermes remains an active branch of the Hermes project; Perry ships a pre-1.0 CLI and platform stack.

Cross-platform UI

Perry vs Electron

Electron embeds Chromium and Node.js and renders application UI as web content. Perry compiles supported TypeScript through LLVM and maps its UI model to platform widgets where supported. Electron is more mature and web-compatible; Perry targets a different UI and deployment model.

Cross-platform UI

Perry vs Tauri

Tauri combines a compiled Rust core with HTML, CSS, and JavaScript rendered in an operating-system webview. Perry compiles supported TypeScript through LLVM and maps Perry UI to platform widgets. Tauri benefits from web frontend compatibility; Perry targets a no-webview UI model.

Cross-platform UI

Perry vs React Native

React Native normally runs JavaScript through Hermes and renders host-platform views through its renderer and native-component system. Perry compiles supported TypeScript through LLVM and statically links its runtime and GC. React Native is much more mature; Perry offers a different AOT and target model.

Cross-platform UI

Electron Alternatives for TypeScript

Four realistic paths for TypeScript desktop apps in 2026: Electron, Tauri, Bun single-file binaries, and Perry's native widgets. Binary size, memory, UI stack, and language compared honestly.