Clojurians
#datascript
<
2016-08-24
>

This page is not created by, affiliated with, or supported by Slack Technologies, Inc.

kurt-yagram09:08:39

just wondering, I was reading https://github.com/Day8/re-frame. The same thing has been done with rum and datascript, however, the guys of re-frame state: > We'd love! to be using datascript - so damn cool - but we had too much data in our apps. the 'too much data in our apps'-part strikes me: did anyone ever had too much data for using datascript? (And if there's too much data for using datascript, I suppose there too much data anyway?)

misha14:08:43

@kurt-yagram depending on your use case. For example, to use datascript in ios app, I had to wrap it up in a separate javascriptcore context and talk to it asynchronously via extra api layer, because pull-many took way too much time (~1second) on iphone 5, even with <1000 datoms. And if in some cases you might be able to tolerate 1second queries, – this is getting painful too fast (my initial payload consists out of 2k entities, not datoms, w/o any user data). However, using it for administration UIs - is :heart:

misha14:08:48

(I use it for ios app anyway to make client(datascript)/server(datomic) data sync much less painful. reduces amount of APIs to write and debug as well)

kurt-yagram14:08:16

allright... pull-many is rather slow? I didn't see datascript very slow with a few 1000s datoms so far, but the queries I usually do are rather basic, no pull-many etc.

misha14:08:36

pull-many with a nested pull-pattern, to be exact

misha14:08:34

@kurt-yagram where did you run your queries? quad-core laptop? or 3-year old android smartphone? (basically that's what I mean by "depending on your use case.")

kurt-yagram15:08:05

yeah, that might be it... 6 year old desktop