Fork me on GitHub
#hoplon
<
2017-06-24
>
thedavidmeister02:06:08

@flyboarder i'm thinking more about integrating with cells somehow rather than replacing

thedavidmeister02:06:22

the thing is that cells + datascript looks nearly identical to precept

thedavidmeister02:06:41

except that cells propagate the value of the database to the entire app every time the db changes

thedavidmeister02:06:08

whereas precept seems to have an algorithm to only propagate to queries that could actually have changed their value

thedavidmeister02:06:45

which seems like it could potentially be a near drop-in replacement for what i'm doing now but with better performance

flyboarder03:06:45

@thedavidmeister right, however in that case it means you are storing your entire db state in a root cell, I'm not sure that's the best way to do it with large databases, small ones sure but IMO i think state on the client side should be scoped to what's relevant to what's on your screen

flyboarder03:06:23

The only place I want all my data at once is in my db

thedavidmeister05:06:36

@flyboarder it is client state that is relevant to what's on the screen

thedavidmeister05:06:15

for me, it's tied to something that updates on keypress, so anything 20ms+ causes some jank

thedavidmeister05:06:58

and datascript queries for even modest databases and queries can weigh in at 10ms+

thedavidmeister05:06:57

i'm working around it OK for the moment by shifting to directly handling datoms on the critical performance path but this sacrifices a lot of what makes datascript useful in the first place

flyboarder21:06:34

right, makes sense

flyboarder21:06:32

Here is a peek at the next css lib im working on for Hoplon