Infrastructure July 27, 2026 mixed ⇧ 353 pts across 2 threads

Escape from Runtime: Native Compilation Gains Serious Traction

Vercel dropped Scriptc, a TypeScript-to-native compiler that produces self-contained binaries with no JavaScript engine bundled inside. The thread immediately lit up with comparisons to Porffor, an independent project chasing the same goal, and PerryTS/pry, another entrant. The 178kb binary size drew mockery ('What are you putting in there, a JVM?') but also genuine interest from people who have long wanted to ship a TypeScript CLI or server without dragging a Node.js install along.

The Bun Rust rewrite thread hits the same nerve from the opposite direction. The author found that Bun's progress on its Rust rewrite is slower than the public narrative implied, and the comment thread was pointed: 'If you've ever worked at a tech company you already know the answer without reading any further.' Triumphalist developer blog posts, whether from Bun or anyone else, are increasingly being stress-tested by independent tracking.

The pattern here: there is real appetite for TypeScript tooling that doesn't require a heavyweight runtime, but the implementation is harder than it looks. Multiple projects are converging on the same problem at once, which usually means a solution is 18 to 24 months away from being genuinely useful for production workloads.


So what?

If native TypeScript compilation becomes reliable, it changes the deployment story for CLI tools, edge functions, and small services. Founders building developer tools should watch Scriptc and Porffor closely. The Bun lesson is equally relevant: be skeptical of rewrite announcements until you see shipped artifacts, not blog posts.

Read these