This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-06-24
Channels
- # beginners (12)
- # boot (15)
- # chestnut (1)
- # cljs-dev (24)
- # cljsrn (2)
- # clojure (32)
- # clojure-dev (9)
- # clojure-news (1)
- # clojure-spec (7)
- # clojurescript (17)
- # cursive (12)
- # datomic (13)
- # hoplon (13)
- # instaparse (8)
- # jobs (3)
- # luminus (11)
- # lumo (10)
- # off-topic (2)
- # parinfer (2)
- # pedestal (2)
- # protorepl (3)
- # slack-help (1)
- # sql (6)
- # vim (1)
@flyboarder i'm thinking more about integrating with cells somehow rather than replacing
the thing is that cells + datascript looks nearly identical to precept
except that cells propagate the value of the database to the entire app every time the db changes
whereas precept seems to have an algorithm to only propagate to queries that could actually have changed their value
which seems like it could potentially be a near drop-in replacement for what i'm doing now but with better performance
@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
The only place I want all my data at once is in my db
@flyboarder it is client state that is relevant to what's on the screen
for me, it's tied to something that updates on keypress, so anything 20ms+ causes some jank
and datascript queries for even modest databases and queries can weigh in at 10ms+
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
right, makes sense
Here is a peek at the next css lib im working on for Hoplon