On this release we’re showing what you can do by taking the modern web standards — HTML, CSS, and JS — to their absolute peak:
The entire app is significantly lighter than a React button:
See benchmark and details here ›
Going large-scale
Here’s the same app, now with a Rust computation engine and Event Sourcing for instant search and other operations over 150,000 records — far past where JavaScript (and React) would crash with a stack overflow error:
See this demo live ›
Nue crushes HMR and build speed records and sets you up with a millisecond feedback loop for your day-to-day VSCode/Sublime file-save operations:
Here’s what this means:
For Rust, Go, and JS engineers
This is a wake-up call for Rust, Go, and JS engineers stuck wrestling with
15 Comments
tipiirai
Nue’s a web framework I’m building to slice through modern web dev bloat. When a Vite/ShadCN/Tailwind button is 40% heavier than a full-blown SPA, it’s time to do things differently. We’re retooling from the ground up—web standards first, no bloat. It’s for frontend architects, design engineers, and UX folks craving simpler, saner workflows. Still in progress, but the shift’s coming. Curious to hear your thoughts!
tipiirai
Not an April fool's joke btw!
mirzap
> 150,000 records — far past where JavaScript (and React) would crash with a stack overflow error
I think react-virtualized and stack tables can easily handle 1 million rows client-side without a problem (I saw the demo somewhere).
Web development is about convenience, and the speed of development is far more important than ultra optimizations. People simply don't care about super optimizations because servers are so fast these days, and bandwidth is cheap, almost free.
But it's an interesting project. Good luck.
wordofx
The animation makes it look so incredibly slow…
mary-ext
The animations makes it feel slow, the lack of any throttling/debouncing means that my input feels slow too.
wetpaws
[dead]
m00dy
why would 150,000 records break React and throw overflow exception ?
leonhard
I really like the approach but the demo [0] doesn’t really work on iOS Safari (although might be my outdated 16.7.8 version).
Scrolling doesn’t work, the layout and buttons have weird line breaks, the native search button is embedded in the custom designed one, leading to 2 icons…
[0] https://mpa.nuejs.org/app/
handfuloflight
Would you be able to hook this up to https://www.convex.dev/?
n2d4
Are there any code examples? I've looked for a bit but haven't found any. That should IMO be the first thing on any blog post about new frameworks.
farzd
love the demo and overall reason for this, hope it gets the following and support it deserves!
zol
Today it’s Nue. Tomorrow it’ll be Olde and we’ll complain about all the boilerplate or repetitive update logic we now have to write.
Garlef
Looks interesting!
Regarding the code examples in the docs:
It would be great if the examples for models and views would be from the same example.
Currently, the view example is something about users and the model is something about customers?
The interesting part for me is not how the individual components of the architecture work but how they connect…
mentalgear
Congrats, Nue seems to be an impressive and well-thought-out design system & framework. It feels like a strong candidate to become the "Web Standards Stack" —finally freeing developers from the complexity and bloat of modern frontend tooling.
I've been following Nue for a while now, and I'm eager to use it for real world apps. Any updates on when the design system will be released? I know you're ambitious, but I'd suggest launching a single design system first to test the waters, gather feedback, and gain traction — rather than waiting to release everything at once (but losing out to the ecosystem).
throwaway290
1. It's an SSG and competes with projects like Astro or Solid or Next. Comparing to React is apples to oranges.
2. Benchmarks are just numbers without details. React+ReacDOM gzipped/minified is 40 kb in 2025. I doubt a button adds 30 kb. But if you really want to make fast SPAs, Preact is just 4 kb and it doesn't require to learn a new bespoke templating DHTML-style thing.
3. From FAQ
> The WebAssembly example in our demo isn't about raw performance — it demonstrates something far more important: what becomes possible when your business logic is properly separated from presentation.
> But when your business logic lives in its own pure layer, entirely new possibilities emerge. Rust is just one example — you could model complex financial calculations, build sophisticated data visualization engines, or create real-time collaboration systems. Your logic can evolve independently of the interface, enabling the kind of architectural advances that the React monolith prevents.
The writer was high or delusional or bad at explaining the point. Nothing prevents you from putting logic into "its own pure layer" in any language. You can make it messy and impure with Rust/WASM/… and you can keep it pure with pure JS.