This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-03-01
Channels
- # announcements (26)
- # babashka (58)
- # bangalore-clj (1)
- # beginners (48)
- # bitcoin (1)
- # chlorine-clover (9)
- # clara (7)
- # clj-kondo (11)
- # cljs-dev (10)
- # cljsrn (36)
- # clojars (11)
- # clojure (161)
- # clojure-europe (39)
- # clojure-italy (2)
- # clojure-nl (6)
- # clojure-uk (14)
- # clojured (1)
- # clojurescript (38)
- # conjure (25)
- # core-async (18)
- # cursive (19)
- # datascript (9)
- # datomic (11)
- # emacs (10)
- # events (2)
- # figwheel-main (2)
- # fulcro (44)
- # funcool (5)
- # girouette (1)
- # graalvm (6)
- # jobs (1)
- # lsp (93)
- # malli (3)
- # membrane (3)
- # off-topic (17)
- # pedestal (2)
- # polylith (12)
- # re-frame (2)
- # remote-jobs (1)
- # shadow-cljs (47)
- # specter (2)
- # startup-in-a-month (1)
- # tools-deps (4)
Hi! I’m building a PoC webapp as clojure monolith and am weighing the options on whether to include datascript early in the project. I’m trying to pro-con it and here’s my list 1. If the project splits into server+client, how reusable is the datascript logic on Cljs? or the datalog queries on datomic? 2. I know datascript started as a Cljs project. What’s the performance like on JVM? 3. Do I need even datalog at such an early stage? Am I overthinking this? Any ideas is welcomed
1. The queries are mostly the same between datomic and datascript. There are some differences, but a lot of your queries will still work, or needed only minimal modification. 2. JVM performance is much better than on JS engine. 3. The datomic/datascript model is exceptionally flexible and powerful, so why not!?
Also, consider datahike, as this gets you server+client, as well as durability (which datascript itself does not)
Also addresses the issues with the subtle differences between data in datomic & datascript, since you can (potentially at least) have the same db on client and server.
(also would support offline writes for clients, etc)