Rari – Rust-powered React framework • Hacker News Board

Re: Rari – Rust-powered React framework

#81

Post by satvikpendem » Fri, Feb 13, 2026, 6:08 AM UTC

re-thc wrote: post #48

Would be more interesting to compare this to Bun or Deno + NextJs or Tanstack Start or React Router performance wise.

The author said it achieves ~50x more throughput than Next.

Re: Rari – Rust-powered React framework

#82

Post by pdyc » Fri, Feb 13, 2026, 7:11 AM UTC

mblode wrote: post #51

If 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

demo does not works on firefox+linux

Re: Rari – Rust-powered React framework

#83

Post by rk06 » Fri, Feb 13, 2026, 7:15 AM UTC

catlover76 wrote: post #37

uriahlight wrote: post #35

It'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.

I hate React, but Vue never seemed much better. What is better about it, in your opinion?

no 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

Re: Rari – Rust-powered React framework

#84

Post by re-thc » Fri, Feb 13, 2026, 7:34 AM UTC

satvikpendem wrote: post #81

re-thc wrote: post #48

Would be more interesting to compare this to Bun or Deno + NextJs or Tanstack Start or React Router performance wise.

The author said it achieves ~50x more throughput than Next.

On Node, presumably?

Re: Rari – Rust-powered React framework

#85

Post by BrandiATMuhkuh » Fri, Feb 13, 2026, 8:35 AM UTC

Pretty 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' .

Re: Rari – Rust-powered React framework

#86

Post by tubs » Fri, Feb 13, 2026, 9:08 AM UTC

skiniks wrote: post #30

lionkor wrote: post #24

Earlier quoted context omitted.

V8 is C++, so why isn't it "C++ powered"?

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.

How big is the server runtime compared to v8 under the hood?

Yes, every one of those apps is c++ powered.

Re: Rari – Rust-powered React framework

#87

Post by pjmlp » Fri, Feb 13, 2026, 10:53 AM UTC

uriahlight wrote: post #35

It'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.

I care about what SaaS SDKs support out of the box, I don't have time to yak shaving or do avocacy to our FE teams.

That means it is mostly React/Next.js and in some cases, Angular.

Anything else will get side looks on why are we not using the official SDKs from partners.

Re: Rari – Rust-powered React framework

#88

Post by TonyStr » Fri, Feb 13, 2026, 1:34 PM UTC

profstasiak wrote: post #36

uriahlight wrote: post #35

It'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.

I am a react developer. For past few months I am working in vue and I Just dont see any benefits

Vue 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: Rari – Rust-powered React framework

#89

Post by satvikpendem » Fri, Feb 13, 2026, 3:04 PM UTC

re-thc wrote: post #84

satvikpendem wrote: post #81

Earlier quoted context omitted.

The author said it achieves ~50x more throughput than Next.

On Node, presumably?

Yes

Re: Rari – Rust-powered React framework

#90

Post by mblode » Fri, Feb 13, 2026, 7:37 PM UTC

pdyc wrote: post #82

mblode wrote: post #51

If 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

demo does not works on firefox+linux

Is there a way to enable WebGPU flag on Firefox Linux?