For example: docs.rs/differential...
I don't know that a social network is the kind of problem best (currently) suited for sync engines.
For example: docs.rs/differential...
I don't know that a social network is the kind of problem best (currently) suited for sync engines.
In one spin, a kind of reducer needs to live near where data is persisted. Another kind lives on the clients. The events and actions they reduce may be different but are coordinated to propagate eventually-consistent state.
In one spin, a kind of reducer needs to live near where data is persisted. Another kind lives on the clients. The events and actions they reduce may be different but are coordinated to propagate eventually-consistent state.
That could create quite an inflection point for the go JS tooling ecosystem.
That could create quite an inflection point for the go JS tooling ecosystem.
These would be opt-in graph colour-buster syntax that a sufficiently good compiler could down level. But runtime support would be needed to really unlock the perf potential.
These would be opt-in graph colour-buster syntax that a sufficiently good compiler could down level. But runtime support would be needed to really unlock the perf potential.
Might these let me move on?
Might these let me move on?