▲ | tipiirai 3 days 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 Rust-powered SPA with event sourcing over 150k records—far beyond ‘simple.’ For state-driven apps, Nue’s model-first approach keeps things clean and scalable—limitations are there, sure, but they’re not the foot-shooter you might think. Right tool, right job—totally agree—just saying Nue’s toolbox is bigger than it looks! | ||||||||
▲ | girvo 3 days ago | parent | next [-] | |||||||
> Nue’s model-first approach keeps things clean and scalable Like I understand why you say this, but as someone who spent the 2000s building "model first" web apps (and desktop applications), I don't miss it in the slightest. Immediate mode-esque render loops didn't catch on just because it's a fad, it really does fit a lot of highly interactive things better. Of course the bigger problem is people using something that's great for heavily interactive web applications for building things that _don't need_ that interactivity... Nue looks great, and I think it stands on it's own two feet. The constant React bashing just turns me off it more than anything (and that's not about React specifically, I have no real love for it, just that kind of project marketing isn't my cup of tea) | ||||||||
| ||||||||
▲ | maxloh 3 days ago | parent | prev | next [-] | |||||||
Thanks for your reply! The misconception might stem from the lack of clarity in the documentation regarding how islands (components) work. - How do I declare local states (instance variables) in an island? - How do I fetch and display data from an API? - Where should we place data that is normally kept in contexts/stores in other frameworks? These are common problems faced when developing an SPA, but missing in the documentation. | ||||||||
▲ | tombl 3 days ago | parent | prev [-] | |||||||
hmm, it looks like you've got a bug in the demo app. if you type too quickly into the search bar, the entire app slows to a halt. seems like you'd want to move the filtering logic off the main thread, or you'd want to reinvent React's "Fiber" suspendable rendering architecture. |