8 ms·
Rari – Rust-powered React framework
- xlmnxp 7mo agoGet started but not working
- mattrighetti 7mo agoWebsite has been hugged
- tuhgdetzhh 7mo agoThats not good advertising for raris Performance claims.
- skiniks 7mo agoFair 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 rails set too tight. Adjusted now and it's handling the load as expected!
- skiniks 7mo agoAuthor here! Should be all good now, turns out the rate limiter was a bit overzealous
- splix 7mo agoNice project, thank you for working on it. I was trying to figure out the architecture, and I understand that it runs a Deno VM to execute JS on the backend? I was working on something similar, but for JVM backends [1]. And it seems there are a lot to learn from your project. For example, I'm using GraalVM that executes JS on the server. But I have to compile JS to WebAssembly because otherwise it produces a lot integration issues on the backend. Do you do the same? [1] https://github.com/emeraldpay/double-view https://github.com/emeraldpay/double-view
- skiniks 7mo agoThanks 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 Rust bindings to V8's C++ API, which lets us run JS/TypeScript with minimal overhead. We handle module resolution, imports, and the React rendering pipeline all in Rust, then execute the actual component code in V8. No WASM compilation step needed. Your JVM project looks cool! The GraalVM → WASM approach makes sense for JVM integration. We avoid those integration issues by keeping everything in the Rust/V8 ecosystem. The tradeoff is we're tied to V8, but we get native performance and direct access to V8's features.
- splix 7mo agoThat may sound strange, but it turns out I don't use WASM as well. Last time I touched this part was ~8 month ago, and WASM was just one of the experiments, and I forgot about this. Just remember it was hard to find a right approach initially, on how to execute JS without NodeJS environment. But with a right set of polyfills it works now. Anyway, I see we have a bit different approaches on how to handle JS part, and I could get some ideas from that.
- samrith 7mo agoI went through the website. But I do have a one question - it is not immediately clear to me why I'd use rari over Actix or just a plain-old Express server? What is "rust-powered performance"?
- dev_l1x_be 7mo ago> React Server Components framework powered by a Rust runtime. If anybody is wondering.
- desireco42 7mo agoThank you, came to comments to find out what it is. Now I can go back to site and see what it is about. Thanks again.
- satvikpendem 7mo agoIs this like ReasonML and its React-Reason framework? I don't really understand how it works, what part is Rust powered, is it reimplementing the JS engine in Rust?
- bsimpson 7mo agoI forgot all about Reason…
- moritzwarhier 7mo agoI once (2022 I think) took a short ReasonML course with hands-on and while it was only superficial, I remember how much it increased the appeal of pattern matching and immutability for me... without being a true FP head or anything.
- skiniks 7mo agoNot 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 server underneath. You write React → Rust server executes it → better performance than Node-based alternatives.
- laurencerowe 7mo agoHow is this different than running that same React code in deno whose HTTP server is also written in Rust?
- skiniks 7mo agoThe 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 optimized. rari also uses Axum for the HTTP layer with opinionated defaults for RSC workloads: streaming responses, proper cache headers, and optimized middleware are all configured out of the box. While we use Deno's excellent crates (deno_core for V8 bindings, we're big fans of the project!), you're not locked into the Deno ecosystem. rari uses standard node_modules resolution, so your existing Node/npm workflows just work. Think of it like this: Deno gives you a runtime to build on, while rari gives you the full stack with integrated bundler, router, HMR, and dev server all configured to work together for RSC apps.
- mpeg 7mo agook so I actually like this, but the description and documentation in general are terrible "rust-powered" meaning it uses rolldown to bundle the javascript, that's fine, but it's a weird thing to highlight, it's confusing for people that aren't super familiar with vite and might think this is a rust framework from the docs "one of rari's superpowers is seamless NPM package integration" this makes me think the docs are LLM-written... npm package integration, like every other javascript library. now, the good: there's very few simple frameworks for react (react router and tanstack) and I think the simplicity here on going from an empty project to RSCs is absolutely great, and should be the tagline I was also happily surprised at how mature the codebase is in comparison to the docs, the vite plugin actually supports a lot of the options I would have expected to see, they're just not documented yet edit: I realised after digging a bit deeper this actually does have a rust runtime that runs the js, that was not very clear... is this separate from the framework or does the framework only run in the rust runtime? eg can it run on node?
- skiniks 7mo agoYou'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 the bundler. The actual HTTP server, RSC renderer, and routing are all written in Rust (using an embedded V8 engine to execute your React components). It's not just Rolldown doing the bundling. On the npm integration point: what I should have said is that rari's Rust runtime handles traditional node_modules resolution (require/import from node_modules), which is actually pretty rare for Rust-based JS runtimes. Deno, for example, uses npm specifiers instead of node_modules. Great feedback on the tagline too. "Zero to RSC in minutes" is way clearer than what we have now. The codebase is definitely ahead of the docs, I've been focused on getting the runtime solid first, but clearly need to catch the documentation up. Thanks for taking the time to dig in and give constructive feedback. This is exactly the kind of input that helps make it better.
- mpeg 7mo agoYeah I wrote my comment initially thinking it was just rolldown being used, so the "rust-powered" was confusing, I think the tagline is actually ok now that I know this, but really you're doing two things here 1/ an alternative framework for RSCs similar to nextjs, tanstack or react router 2/ a rust runtime for javascript, similar to node, deno or bun (except maybe not as general purpose)
- dbacar 7mo ago"Rust-Powered Performance Native speed with Rust compilation for blazing-fast builds and runtime" It seems only Rust itself compiles slow while helping others brag about it :).
- deleted 7mo ago[deleted]
- zadikian 7mo ago"I guide others to a treasure I cannot possess"
- satvikpendem 7mo agoruntime != compile time
- rtcode_io 7mo ago[flagged]
- sebringj 7mo agothis looks neat and reminds me of "Ferrari" for fast and combines "react" so it's a great name. Was there a specific use case for this that inspired you? I would imagine some massive existing heavy thing that you plugged in to fix to save it? I just put my open source thing out so it's nice to see some traction on yours, rooting for you.
- skiniks 7mo agoThank 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 straightforward: I wanted to build something for myself that was as performant as I could make it. I'd been using Rust a lot more in my day-to-day work and wanted to see if I could bring those performance benefits to React development without forcing JS devs to write Rust. The goal was to abstract away the complexity of Rust but still deliver the same benefits. Congrats on shipping your project! What did you build?
- sebringj 7mo agoah gotcha... i was picturing like this massive web page that was dog slow that you just like made mad fast... but that's cool though. I'll run it. I built autonomo on github, it's this mcp you plugin to your whatever ai editor and it drives the app/web/desktop whatever thing and validates it actually runs and works... keep building homie!
- choiway 7mo agoNaming so lit
- skiniks 7mo agoThanks twin!
- uriahlight 7mo agoIt's like beating a dead horse. React is the literal worst of all the modern JavaScript frameworks and yet that's what everybody insists on using. Vue is light years ahead of it (and will be even further ahead when the new Vapor mode is released in 3.6). Svelte is ahead. Solid is ahead. Heck, even Marko is ahead.
- catlover76 7mo agoI hate React, but Vue never seemed much better. What is better about it, in your opinion?
- rk06 7mo agono weird rules of hook. automatic dependency tracking. no stale closure gotchas, no running hook 1000 times cause you made a mistake. Better update performance by default. definitely better dev tools
- catlover76 7mo ago[dead]
- profstasiak 7mo agoI am a react developer. For past few months I am working in vue and I Just dont see any benefits
- uriahlight 7mo agoThou art living under a rock.
- satvikpendem 7mo agoIronic.
- TonyStr 7mo agoVue should be a bit faster due to signals (updating state doesn't cause whole components to rerender), or at least require a bit less work to optimize (not as much need for useMemo, useEffect, etc. if everything uses signals). Other than that, it's mostly up to personal preference. SFC, directives, etc. are all just developer ergonomics, and people tend to prefer whatever they're most used to. Also, vue interops better with webcomponents and non-framework code than React in my experience. Most non-React libraries need a React wrapper to work in a React project.
- re-thc 7mo agoWould be more interesting to compare this to Bun or Deno + NextJs or Tanstack Start or React Router performance wise.
- satvikpendem 7mo agoThe author said it achieves ~50x more throughput than Next.
- re-thc 7mo agoOn Node, presumably?
- satvikpendem 7mo agoYes
- CrociDB 7mo agoI understand nothing of frontend, and never even saw what React looks like, what is this supposed to be? Is it compiler--written in Rust--of React whatever to actual Javacript with DOM calls?
- skiniks 7mo agorari 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 engine that executes your React code on the server. Think of it as a faster alternative to Node.js for running React Server Components. You still write normal React code, but the server-side execution happens in Rust instead of Node.js, which gives it massive performance gains (46.5x higher throughput than Next.js). It handles routing, server-side rendering, and serves both server components (rendered on the server) and client components (interactive JavaScript sent to the browser). The output is still HTML + JavaScript that runs in the browser—just generated much faster.
- mblode 7mo agoIf anyone’s exploring Rust + React, I’ve been building something similar on the rendering side. react-vello [1] exposes Vello (a Rust GPU renderer) as a React renderer via WASM + WebGPU, so you can draw shapes and text declaratively while Rust handles the rendering in the browser. [1] https://github.com/mblode/react-vello https://github.com/mblode/react-vello
- ipnon 7mo agoVery nice, I think a Rust server using a WebSocket to send MorphDOM diffs to the browser would be very well received.
- skiniks 7mo agoThis is very cool!
- ChadNauseam 7mo agoRust + React is a beautiful combination. For my project, I use Rust for the actually complicated logic that needs to be correct and performant. And then I just use React for the UI. It works pretty great. The communication between the two with wasm-bindgen and tsify is just so easy. It's almost as if they're the same language. It's really crazy, honestly. A feat of engineering. React Vello seems super cool, by the way. Thanks for sharing it!
- satvikpendem 7mo agoSimilar to Dioxus Native I imagine?
- pdyc 7mo agodemo does not works on firefox+linux
- mblode 7mo agoIs there a way to enable WebGPU flag on Firefox Linux?
- ivanjermakov 7mo agoFor those looking for an actual Rust web framework, check out Leptos: - https://leptos.dev/ https://leptos.dev/ - https://news.ycombinator.com/item?id=36461660 https://news.ycombinator.com/item?id=36461660 - https://youtu.be/cp3tnlTZ9IU?si=5H4cAVS8g6CFGwab https://youtu.be/cp3tnlTZ9IU?si=5H4cAVS8g6CFGwab
- skiniks 7mo agoThanks 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 React Server Components framework that happens to be powered by a Rust runtime. The goal is to abstract away Rust's complexity entirely so JavaScript/TypeScript developers can build high-performance React apps without needing to learn Rust.
- giancarlostoro 7mo agoI've dreamed of someone taking React and making it somehow embeddable to any back-end programming language without a performance hit, so you can blend it with .NET, Go, Django, etc and it would run either natively or alongside said platform. This is impressive.
- skiniks 7mo agoThank you!
- thr0waway001 7mo agoJust a word of caution. According to my buddy there’s a famous rotund corn star named Rari or Rhari so she might come up in the search results.
- fulafel 7mo agoThe docs start off with server components. Are those still in vogue after the recent security disaster? ref. https://threatprotect.qualys.com/2025/12/04/react-server-components-rsc-remote-code-execution-vulnerabilities/ https://threatprotect.qualys.com/2025/12/04/react-server-com...
- BrandiATMuhkuh 7mo agoPretty cool work! Question: what's the difference in using BUN? I'm currently using buns react frontend/backend system. And afaik it's also written in rust. The part that I don't see are the 'use server' .