This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-11-05
Channels
- # 100-days-of-code (1)
- # announcements (7)
- # beginners (84)
- # boot (1)
- # cider (22)
- # cljdoc (14)
- # cljs-dev (45)
- # cljsrn (6)
- # clojure (65)
- # clojure-conj (7)
- # clojure-finland (1)
- # clojure-italy (7)
- # clojure-nl (2)
- # clojure-serbia (1)
- # clojure-uk (111)
- # clojurescript (58)
- # cursive (8)
- # datomic (68)
- # duct (1)
- # emacs (33)
- # figwheel (3)
- # figwheel-main (9)
- # fulcro (33)
- # graphql (1)
- # juxt (30)
- # kaocha (4)
- # off-topic (22)
- # pathom (47)
- # pedestal (4)
- # planck (6)
- # re-frame (1)
- # reagent (1)
- # reitit (13)
- # shadow-cljs (49)
- # spacemacs (7)
- # sql (6)
- # tools-deps (60)
hi all, what libraries do you recommend for data persistence (just Clojurescript app state) in react native app? I guess performance should be a concern
Either http://realm.io (slow to read in dev mode but faster in general) or just plain AsyncStorage
Even though it’s bad practice it’s very nice to serialize the data with transit since it’s much faster than pr-str
@vikeri how come that's bad practice?
I've been using async storage + transit 🙃
I have a post a couple days back about using UserDefaults to store data, but it’s iOS-only. If I were working cross-platform I’d just use AsyncStorage and pr-str
/`read-string`. I’ve never seen any performance problems with them, but I’m not storing MB of data either.