skiniks

3 ms·

1.
A Rust runtime for React that hits 97k req/s by keeping V8 idle(rari.build)
3 points by skiniks 4mo ago|0 comments
2.
by skiniks 8mo ago
I appreciate constructive feedback, but the assumption that the docs were rushed with an LLM isn't accurate. I've spent over a year on this project. That said, I hear you on the messaging and I'm working to improve it. Cheers
3.
by skiniks 8mo ago
I'm not a zoomer, and you literally posted "I am person who rushes". Take a second after touching grass, then proofread your posts.
4.
by skiniks 8mo ago
Where did I say they were rushed with an LLM? I've spent countless hours on the framework, and the docs, and have been clear that I'm open to PRs to help with the copy. This isn't something that was rushed in the past few day
5.
by skiniks 8mo ago
Thank you!
6.
by skiniks 8mo ago
This is very cool!
7.
by skiniks 8mo ago
rari is a React Server Components framework with a Rust-powered runtime. It's not a compiler that converts React to vanilla JavaScript—it's a full framework (like Next.js) that runs React applications. The Rust part is the runtime
8.
by skiniks 8mo ago
Thanks for sharing Leptos! I'm actually a fan of it too, it's a great framework for those who want to build full-stack apps in Rust. That said, rari takes a different approach. It's not a pure Rust framework. It's a Reac
9.
by skiniks 8mo ago
Thanks twin!
10.
by skiniks 8mo ago
Thank you, that's very kind! The name actually comes from "Runtime Accelerated Rendering Infrastructure" (RARI), but I love the Ferrari connection, it definitely fits the performance theme. The inspiration was pretty straight
11.
by skiniks 8mo ago
Exactly! Those are the two main layers. The runtime piece is definitely less general-purpose than Node/Deno/Bun. It's optimized specifically for React Server Components with things like streaming, Suspense boundary handling,
12.
by skiniks 8mo ago
Technically you could say that, but the entire server runtime is written in Rust. V8 is just the embedded JavaScript engine. By that logic, every Node.js or Deno app would be "C++ powered" since they all use V8.
13.
by skiniks 8mo ago
Thanks for checking it out! rari uses V8 (via deno_core bindings) embedded directly in the Rust runtime, not a full Deno VM. We execute JavaScript directly on V8 without compiling to WebAssembly. The key is that deno_core provides clean Rus
14.
by skiniks 8mo ago
The main difference is that Deno doesn't have React Server Components support. You'd need to build the entire RSC runtime yourself (streaming, Suspense boundaries, server actions, etc.), whereas rari has this built in and optimize
15.
by skiniks 8mo ago
You're right about the messaging being confusing, I've been writing everything solo, so I'm definitely open to PRs that help with the copy. To clarify: "Rust-powered" refers to the server runtime itself, not just th
16.
by skiniks 8mo ago
Not like ReasonML, you still write normal React/TypeScript. The Rust part is the server runtime. Instead of Node.js running your React Server Components, rari uses a Rust server with an embedded V8 engine. Same React code, different se
17.
by skiniks 8mo ago
Fair point! To be clear: rari handled the traffic perfectly fine - the issue was an overly defensive rate limiter I had configured (and it was grouping proxy traffic incorrectly). The framework itself was cruising, I just had the safety rai
18.
by skiniks 8mo ago
Author here! Should be all good now, turns out the rate limiter was a bit overzealous
19.
by skiniks 1y ago
Author here. We added proper app router support, SSR, and correct RSC semantics to Rari. The performance improvements were dramatic: - 0.69ms avg response (3.8x faster than Next.js) - 20,226 req/sec throughput (10.5x higher) - 4ms P99
20.
The Rari SSR Breakthrough: 12x Faster, 10x Higher Throughput Than Next.js(ryanskinner.com)
1 points by skiniks 1y ago|2 comments
21.
How I Built a Full-Stack React Framework 4x Faster Than Next.js(ryanskinner.com)
3 points by skiniks 1y ago|1 comments
22.
by skiniks 1y ago
After 25 years of web development, I built Runtime Accelerated Rendering Infrastructure (Rari) to prove that React frameworks can be both developer-friendly and exceptionally fast. Key results vs Next.js: - 4.04x faster component rendering