Re:No-build, no-NPM, SSR-first JavaScript framework if you h...
by Jenk on Tuesday March 24, 2026 @09:44AM
(#47502511)
Might be naive, but this has always been a concern of the view-model for me. Every GUI change results in a VM change via event/command. The VM becomes gospel for UI state which means reducers are much simpler, and my actual model doesn't care if it is indeed a button, expando, radio button or whatever else.
Re:No-build, no-NPM, SSR-first JavaScript framework if you h...
by codethief on Wednesday March 25, 2026 @07:38AM
(#47515991)
Isn't React pretty much a model-view-viewmodel architecture?
Re:No-build, no-NPM, SSR-first JavaScript framework if you h...
by Jenk on Wednesday March 25, 2026 @08:28AM
(#47516436)
Yes but it is easy to abuse/misuse IME, in that I think it requires one to maintain your own sense of discipline for the principle separation rather than the library/framework guide you into it. The threshold between UI and state management is comically easy to confuse.
Not dismissing it, mind, that inherent guidance is not something that is easy to achieve and I much prefer working with the likes of React than without.
Re:No-build, no-NPM, SSR-first JavaScript framework if you h...
by whstl on Tuesday March 24, 2026 @11:03AM
(#47503708)
I'm not defending this model anywhere. I'm just stating that React can do what applfanboysbgon suggested: "As a game developer working in my own engine, UI is unbelievably straight-forward: [...]"
"just" is doing a lot of heavy lifting here. Where do you store "pure" GUI state (button state, is expandable expanded, …)? Do you really want to setup Redux for this? (And no, the DOM is not an option in non-trivial cases.)