Comment Comment by adamzwasserman The state encapsulation concern is exactly what DATAOS addresses: dataos.softwareThe premise is that React's "UI=f(state)" creates a synchronization problem that doesn't need to exist.If the DOM is the authority on state (not a projection of state held elsewhere), there's nothing to sync. You read state from where it already lives.I built multicardz on this: 1M+ cards, sub-500ms searches, 100/100 Lighthouse scores.If you have time to read, I would very much like to hear your thoughts; genuine technical pushback welcome. parent adamzwasserman 10 months ago
The premise is that React's "UI=f(state)" creates a synchronization problem that doesn't need to exist.
If the DOM is the authority on state (not a projection of state held elsewhere), there's nothing to sync. You read state from where it already lives.
I built multicardz on this: 1M+ cards, sub-500ms searches, 100/100 Lighthouse scores.
If you have time to read, I would very much like to hear your thoughts; genuine technical pushback welcome.