tipiirai

9 ms·

91.
by tipiirai 2y ago
Would love to get some help on documenting Nue! Crazy amount of work for a non-native English speaker doing both coding and docs.
92.
by tipiirai 2y ago
I think you're right on the marketing. I'll tone down. The comparison uses the non-wasm version at mpa.nuejs.org
93.
by tipiirai 2y ago
Nue JS reactive library is based DOM diffing. The next version also has keyed rows.
94.
by tipiirai 2y ago
Please. It's me typing: Tero "tipiirai". I’m Finnish, not a bot. Documentation? Mostly me, some help from contributors. Comments here? Check my HN history. This stuff is impossible to prove.
95.
by tipiirai 2y ago
Author coming out here: Types matter, and Nue’s take is to use them where they truly shine. Adding them to naturally untyped spots like HTML or CSS? That’s just extra weight we can skip.
96.
by tipiirai 2y ago
Thanks! Definitely going to use `new EventTarget()` in Nue. So obvious. https://nuejs.org/
97.
by tipiirai 2y ago
Author here: Fair point—React’s baseline isn’t a monster. ~60KB compressed for a barebones Vite/React setup, or even ~25KB with Vue. Medium projects at 200-300KB are definitely workable. But here’s the point: a single React/ShadC
98.
by tipiirai 2y ago
Author here: You’re right that Nue shines for simpler sites—like marketing pages, blog, and documentation. But calling it just a static site generator misses the mark. This latest release (check mpa.nuejs.org/app/?rust) handles a
99.
by tipiirai 2y ago
Spot on. HTML, JS, and CSS deliver a clean separation of concerns—a perfect blank slate for killer products. You just need a few key pieces to tie it all together: templating with loops for repeating HTML chunks and a way to stitch in heade
100.
by tipiirai 2y ago
Author here. React’s absolutely mature—no question there, with a skilled team behind it. But the button example highlights something off: a single component outweighing an entire app feels fundamentally broken. There’s clear room for fresh
101.
by tipiirai 2y ago
Author here. You’re spot on. I took away the React association and added a direct link to the JS code [1] that hit the ‘Maximum call stack size exceeded’ wall. TypedArrays can do wild stuff, no doubt, but yeah, it’s not exactly vanilla JS—a
102.
by tipiirai 2y ago
Author here: It’s true—Nue’s view layer is untyped. That’s by design. React’s ecosystem has devs slapping TypeScript on everything—even CSS—which is overkill. Nue flips it: presentation stays clean and semantic, web standards do the heavy l
103.
by tipiirai 2y ago
If you're architecture is based on event sourcing, this is kind of the point
104.
by tipiirai 2y ago
Gotcha. This is something Nue will tackle later trough design systems, where motion design is an option to choose, ditch, or tweak.
105.
by tipiirai 2y ago
Author here. No need to update the resume yet—titles do keep shifting! React’s monolithic style has muddied the waters, making it tough to build clean business logic, prioritize performance, craft CSS design systems, or just focus on user e
106.
by tipiirai 2y ago
The Nue button demo isn’t claiming to replicate every feature of the Vite/ShadCN bundle—no variants, states, or loading spinners here, just a lean example to show size and simplicity. The point’s not to ‘beat’ ShadCN at its own game bu
107.
by tipiirai 2y ago
I’m the author. To clarify: a button installed via ShadCN/Vite’s official docs ( https://ui.shadcn.com/docs/installation/vite ) ends up way heavier than a full Nue SPA. It’s not a jab at React devs—just showing
108.
by tipiirai 2y ago
Thanks for the take—glad you think the project’s cool. I get where you’re coming from: React’s a rendering layer for folks who want control, while Nue’s tackling a broader scope, closer to Vue/Astro/Next combo. The ‘takedown’ vibe
109.
by tipiirai 2y ago
I'm eager to dive into the design systems, definitely coming. But first, I wanted this release to prove Nue isn’t just for ‘hobby projects,’ a label plain website generators often get stuck with. This SPA demo was key—showing how worki
110.
by tipiirai 2y ago
They are from the same example. Here's the source code: https://github.com/nuejs/nue/tree/master/packages/examples/s... Look for "view" and "model" folders
111.
by tipiirai 2y ago
> People simply don't care about super optimizations Could be, but some optimizations in Nue really stand out. Check out bundle size, HMR speed, build speed, and especially repository size. An empty Next.js project weighs over 300MB
112.
by tipiirai 2y ago
How is the SPA less than the button?
113.
by tipiirai 2y ago
There are currently two examples: - `nue create simple-blog` This highlights content-driven websites. - `nue create simple-mpa` This is today’s SPA demo, where 'MPA' stands for multi-page applications. It shows how client-
114.
by tipiirai 2y ago
Fair point—new tools pop up constantly, often just piling more layers on React’s bloated stack. Nue’s not that. It’s a fresh start, built on web standards and closer to the metal, not another abstraction treadmill. That’s why a button can b
115.
by tipiirai 2y ago
The exact error is "Maximum call stack size exceeded" when the WASM- engine is replaced with this JS engine: https://github.com/nuejs/nue/blob/master/packages/examples/s... There is c
116.
by tipiirai 2y ago
I get the same numbers. Interestingly, JavaScript performs faster below 100,000 entries due to the lack of a JS-to-WASM bridge, but it eventually crashes when the records keep increasing
117.
by tipiirai 2y ago
If you look at the documentation at nuejs.org/docs, you'll see how Nue is really more about apps that focus on content rather than single-page apps (SPAs). However, this release is all about SPAs.
118.
by tipiirai 2y ago
Yes. React runtime included. Benchmark and details here: https://nuejs.org/docs/react-button-vs-nue.html
119.
by tipiirai 2y ago
Because that demo crashes with vanilla JavaScript at around 110,000 records
120.
by tipiirai 2y ago
Are you talking about this 150,000 record Rust version? https://mpa.nuejs.org/app/?rust

More ›