the claim of "no runtime" is a bit dubious... you're telling me that you're statically linking a full, modern UI library into every app?

Fascinating. I've written cross platform (WASM, iOS, Android) libraries with Rust before and had a good time but Rust can be a pain too. Cross-platform Typescript is a really interesting proposition.

Though I do worry they're trying to do too much here. Cross-platform TS and native UI libraries? I think the former is much more valuable than the latter. Also doesn't inspire confidence that the text on the site is very clearly AI generated.

Calling a couple million lines of ai written Rust "stable software" is a bold statement

Curious where on spectrum compiling to wasm falls between art project & optimization potential. Should be able to make some nice interfaces between TS-wasm & TS-web

Perry uses NaN-boxing to preserve TypeScript's dynamic type system at runtime, the same approach as JavaScriptCore. The PERF_ROADMAP is honest about the cost: 1.86x behind Zig on image convolution, with 1.24 billion wasted instructions traced specifically to NaN-box unboxing. You cannot get C-level performance without dropping TypeScript semantics, and dropping them means you are no longer compiling TypeScript.