This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-06-02
Channels
- # aleph (5)
- # beginners (112)
- # boot (137)
- # cider (10)
- # cljs-dev (36)
- # cljsrn (2)
- # clojure (118)
- # clojure-argentina (1)
- # clojure-berlin (1)
- # clojure-brasil (3)
- # clojure-dev (4)
- # clojure-italy (2)
- # clojure-nl (13)
- # clojure-russia (23)
- # clojure-spec (5)
- # clojure-uk (53)
- # clojurescript (344)
- # clojutre (1)
- # core-async (65)
- # cursive (9)
- # datascript (7)
- # datomic (28)
- # devops (1)
- # emacs (16)
- # events (1)
- # jobs (5)
- # keechma (18)
- # lumo (56)
- # off-topic (7)
- # om (3)
- # onyx (14)
- # protorepl (21)
- # re-frame (3)
- # reagent (20)
- # ring (12)
- # ring-swagger (9)
- # specter (17)
- # unrepl (14)
- # vim (14)
- # yada (22)
Hey everyone, at work we’ve got a fairly large re-frame project and it feels like we’re out growing the giant map atom approach, so are considering switching to Datascript as the store for our client db. Does anyone have any feedback, advice, or criticism on using Datascript in production?
@colindresj speed might be the only concern, e.g. if your app should run on fairly old android device
@misha thanks for the input — that sounds good. Have you good experience working with it on deployed sites?
Have you come across any pain points or gotchas yet?
We’re really intrigued by Datascript, but just concerned about it’s ability to scale in a true client-facing production environment
Not because we think there’s anything inherently wrong with it, but just because we don’t know of anyone putting it to the test in that setting just yet