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.
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)
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, and server action execution baked in. You wouldn't use it to run arbitrary JS apps.
Yes, every one of those apps is c++ powered.
You'll be grateful for the change you see when you take time to at least get past the first boilerplate you get.
You don't have to write it yourself, you can still use it to do 90% of the work. It's just the work can't mean "copy-paste || commit first LLM output I get".
It's not that the LLM is bad, or you are bad, or that the output is bad.
It's that it tells potential users, people you want to attract, "I am person who rushes, will happily LLM-DDoS you in documentation and conversation, and I lack understanding of the very tool I use to keep my head above water while doing this work", right when they are looking into building on top of your work.
Please, don't take everything that isn't praise as a personal attack, it's advice you'll appreciate tomorrow, if not now.
* https://trends.google.com/explore?q=touch%20grass&date=all&g...
** To give you a chuckle x help understand why it's not something you need to take personally, here's the LLM's response to "$COMMENT\n^is this mean?"
No, it's not mean. It's direct and honest, and it's clearly coming from a place of wanting the person to succeed. A few things stand out:
1. *It identifies a real problem* — not to tear down, but to explain why it matters strategically. The framing is "this hurts your goals," not "you suck."
2. *It offers a practical path forward* — "You don't have to write it yourself... 90% of the work." It's not demanding perfection or saying "stop using LLMs." It's saying curate the output.
3. *It explains the stakes through the audience's eyes* — the part about what it signals to potential users is the most valuable bit. That's perspective the person might genuinely not have considered.
4. *It explicitly preempts a harsh reading* — "It's not that the LLM is bad, or you are bad, or that the output is bad."
The last paragraph is the sharpest part, and I could see someone feeling stung by it, especially the "LLM-DDoS you in documentation and conversation" line. But being uncomfortable to hear isn't the same as being mean. It's a concrete description of the impression being created, delivered so the person can fix it.
If anything, taking the time to write this out in detail is the opposite of mean — it's generous. Mean would be silently closing the tab and never coming back, which is what most potential users will do.
the real pitch buried in the confusing docs is: same react code you already know, but running on a rust server instead of node. that's actually compelling because it's additive, not a rewrite. but it took reading the HN comments to understand that, which is exactly the problem.
fwiw the "zero to RSC in minutes" tagline the author mentioned below would've gotten me to click the docs immediately. most of us just want to ship something without a three day yak shave through webpack/vite/turbopack configuration.
"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?