This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-06-16
Channels
- # aws-lambda (1)
- # bangalore-clj (2)
- # beginners (121)
- # boot (23)
- # cljs-dev (165)
- # cljsrn (8)
- # clojars (2)
- # clojure (164)
- # clojure-berlin (6)
- # clojure-chicago (3)
- # clojure-italy (5)
- # clojure-nl (1)
- # clojure-russia (4)
- # clojure-serbia (32)
- # clojure-sg (1)
- # clojure-spec (8)
- # clojure-uk (55)
- # clojurescript (94)
- # cursive (21)
- # datomic (30)
- # events (1)
- # hoplon (6)
- # jobs (1)
- # keechma (1)
- # liberator (2)
- # luminus (8)
- # off-topic (48)
- # om (12)
- # onyx (24)
- # parinfer (15)
- # pedestal (8)
- # re-frame (4)
- # sql (18)
- # test-check (31)
- # unrepl (70)
- # untangled (21)
i’m also very interested in this. i’m very tempted to make the jump with my app because i’m essentially just sending part of a normalized database as a map to the client and filtering through it in my subs to get what I want. I think being able to query and join data automatically would be much easier but no idea what problems i may face, not enough use cases to make a proper judgement
i’m also wondering what’s preventing people from writing a small wrapper around tonsky’s datascript instead of using posh?
hehe — didn’t realize this is exactly what posh is. saw the datascript dependency commented out from the project.clj and assumed it wasn’t using it
i'm thinking that a combo of data-frame||re-posh and lacinia might be extremely cool - each of them would remove significant amounts of ad-hoc repetition from my codebase