What we learned building a Rust runtime for TypeScript

I can't seem to tell exactly what they built. They call it a runtime, but they're using NodeJS?

Did they implement a transpiler in Rust?

They also seem to be calling Rust from JS, but not through wasm...

They seem to be doing something with Rust and http, but they're also just using "Pingora"...

Additionally, their homepage is about 20 fps while scrolling on my phone (pixel 4a, brave)

I would honestly love for someone to explain to me wtf is going on.

UI note in case the creators of this site are reading: having a right-click on the site logo open a special logo-download menu is probably the wrong choice. If I right click on your site logo it's because I want to open your homepage in a new tab while keeping the original blog post open. The current behavior is unexpected and makes it hard to navigate the site.

> First, we knew we wanted to extend Encore to more languages over time, and we'd seen projects like Prisma and Pydantic successfully use a Rust core with bindings into Node.js and Python respectively.

On an unrelated note Prisma decided to rewrite their Rust core in Typescript. https://www.prisma.io/blog/from-rust-to-typescript-a-new-cha...

I like the seeing the avoidance of generics hell. Traitsmaxxing.

Very side note, but really liking seeing Elysia so close to the top on the benchmark list.

I've been using it, and pointing my LLM's to it as example code, because it's type system is so so much better than Hono's. https://elysiajs.com/

I didn't know that it was also flipping fast as frell. (Encore's benchmark is showing them as faster still, of course!)