Write ReactJS in Rust

Rust meets React? Devs cry “Where’s the source?” and call clickbait

TLDR: A Rust-based server template claims you can “write React in Rust,” but the repo ships precompiled binaries and sparse examples. The community calls out missing source, unclear docs, and a title that feels like clickbait, sparking debate over transparency and what this tool actually does.

A bold claim drops: “Write ReactJS in Rust” via Brahma-Firelight—an “ultra fast” Rust server paired with React, TypeScript, and Vite (a speedy build tool). The setup promises hot reloading and API proxy magic, but the community quickly turned into a courtroom. In the thread, skeptics zoomed in on the repo, spotting a big blob of precompiled files instead of readable code. As one user put it, that’s not how many developers picture open source. Another dug deeper, noting the package looks auto-generated and even flagged platform issues.

Others asked the obvious: How do you actually write React in Rust? A commenter begged for examples—like a simple button click—because the docs don’t show how this “Rust front end” thing actually works. And then came the twist: a user called out a title mismatch, saying this seems like backend tooling, not writing React in Rust. Cue jokes like “Rust in my React? More like Rust behind my React.”

The vibe: excitement clashing with suspicion, plus memes about “source vs sauce.” The repo’s here for the curious: github.com/Shyam20001/rsjs. If the goal was to spark debate, mission accomplished; if the goal was clarity, the crowd’s still waiting.

Key Points

  • A template integrates React and TypeScript with Vite, providing HMR for development.
  • Brahma-Firelight is introduced as a Rust-based high-speed server built on Tokio and Hyper.
  • Quick-start commands include npm install, npm run build, and npm run dev.
  • Vite’s dev server can proxy /api requests to a backend at http://localhost:2000 with changeOrigin and secure options.
  • Brahma-Firelight is positioned as an ultra-fast JavaScript framework, with documentation available for more details.

Hottest takes

"I'm not necessarily sure that a massive blob of compiled code is the way to go:" — philipwhiuk
"you uploaded those `.node` files instead of the source code + building scripts?" — ironblood
"This is a wild mismatch from the HN title, this seems to be backend software?" — embedding-shape
Made with <3 by @siedrix and @shesho from CDMX. Powered by Forge&Hive.