Post

It's been *years* (probably since creating nostalgie.dev) that I haven't really written React code. It's *tough*. I just want to work with plain JavaScript state and have React *only* do rendering. But it feels like I'm swimming against the current trying to do so. What abstractions do folks use?

nostalgie.devNostalgieNostalgie is an opinionated, full-stack, runtime-agnostic framework for building web apps and web pages using React.

Lino Le Van

@linolevan.com

I mean, I know you’re using React but Preact signals kill it when it comes to state. I’d have a look if you haven’t already.

12/11/24, 3:20 pm0 reposts0 likes

Geoff Goodman

@goodman.dev

12 Nov 2024

What I'm hoping to accomplish is to have a business logic layer written in a framework-agnostic way and get the view layer to let go of state management. Buying into a different set of state management opinions seems scary. But will check it out!

Ryan

@rschristian.dev

12 Nov 2024

Preact signals (with the React bindings) could work as they're built to be framework agnostic and therefore work standalone. However, given React's model that "UI = fn(state)", I don't think you can separate the two entirely. At best, you're abstracting/hiding the ties between them.

Lino Le Van

@linolevan.com

12 Nov 2024

I find React’s model makes it hard to abstract out in a meaningful way

Ryan

@rschristian.dev

12 Nov 2024

Indeed, but that's largely the goal. The main problem the React model was trying to address is unpredictable UI born from state not being the only driver of UI; ordering, timing, etc. mattered too. It's totally valid to want them separated but you're going to be fighting against React to do it.