datascript

Thanks. Yes happy to hear about other full solutions. By Datomic in the browser you likely mean https://github.com/tonsky/datascript. Full solutions like InstantDB or ConvexDB offer the syncing part, but they don't seem to be doing full incremental queries in the backend, but rather some combination of smart invalidation and then full recalculation of the subscriptions which then get pushed to the clients.

I'm not terribly familiar with graph databases, but perhaps someone who is can explain the advantage of this awfully complicated seeming design. There's gremlin, cypher, yjs, and zod, all of which I understand are different languages for different problems. What's the advantage of using all these different things in one system? You can do all of this in datalog. You get strong eventual consistency naturally. LLMs know how to write it. It's type safe. JS implementations exist [0]. [0] https://github.com/tonsky/datascript

Prototyping a reactive UI library using DataScript[1] as the db and LWJGL as the rendering layer. I just want to see what happens. 1. https://github.com/tonsky/datascript

Is the datalog engine exposed? Is there any way to cache parsed queries? Other datalog engines support recursive queries, which makes my life so much easier. Can I do that now with this? Or is it on the roadmap? I have fairly large and overlapping rules/queries. Is there any way to store parsed queries and combine them? Also, why the same name as the (Lutris) Enhydra java database? Your domain is currently listed as a "failed company" from 1997-2000 (actual usage of the Java InstantDB was much longer) https://dbdb.io/db/instantdb Given that it's implemented clojure and some other datalog engines are in clojure, can you say anything about antecedents? Some other Clojure datalog implementations, most in open source - Datomic is the long-standing market leader - XTDB (MPL): https://github.com/xtdb/xtdb - Datascript (EPL): https://gi

> a great solution would allow me to pick row-vs-column storage on a per-table basis ... and do some in-context computations to decide where to walk to next on the graph You may be interested in Datomic[0] or Datascript[1] [0]: https://www.datomic.com/benefits.html [1]: https://github.com/tonsky/datascript

The article says Datascript. https://github.com/tonsky/datascript

Yes. Perhaps this is a performance choice for DataScript since DataScript does not keep a complete transaction history the way Datomic does? I would guess this helps DataScript process transactions faster. There is a github issue about it here: https://github.com/tonsky/datascript/issues/366

You might like: Datomic https://www.datomic.com xtdb https://github.com/xtdb/xtdb DataScript (not a database though) https://github.com/tonsky/datascript Cozo https://github.com/cozodb/cozo

Hi pests, I don't think the criticism in the comments gives a full picture. I wrote about a particular flavor of datalog, in common use today. [1] [2]. The earliest representation I know which matches the syntax of my essay, was in SICP [3] There's another, more academic form of datalog which looks a lot like prolog. There's lots of similarities and [2] mentions them. [1] https://github.com/tonsky/datascript [2] https://docs.datomic.com/pro/query/query.html [3] https://sarabander.github.io/sicp/html/4_002e4.xhtml

I've been tooling around with "Tuple Database", which claims to be FoundationDB for the frontend (by the original dev of Notion). https://github.com/ccorcos/tuple-database/ I have found it conceptually similar to Relic or Datascript, but with strong preformance guarantees - something Relic considers a potential issue. It also solves the problem of using reactive queries to trigger things like popups and fullscreen requests, which must be run in the same event loop as user input. https://github.com/wotbrew/relic https://github.com/tonsky/datascript Having a full (fast!) database as my React state manager gives me LAMP nostalgia :)

ICYMI, there's an excellent interactive introduction to `datalog` that's referenced in the article's references.[0] Last time I used `datalog` was years ago, I was developing an internal interactive tool that was used to compare different approaches to solving a certain problem at my employer. I used `datascript`[1] by way of clojurescript to store all experiment data and then interrogated the `datascript` DB via `datalog`. This is something I always remember fondly. [0] https://www.learndatalogtoday.org/ [1] https://github.com/tonsky/datascript

Datascript is the open source analog for Clojure, ClojureScript and JS: https://github.com/tonsky/datascript

I think the Roam Research style backlinked knowledge management apps are directly enabled by datascript. Two "copy cats" (not meant to be derogatory) of Roam that are open source are: https://github.com/logseq/logseq https://github.com/athensresearch/athens The underlying in memory datalog style database that can run in the browser that enables these apps https://github.com/tonsky/datascript

This look nice ! Datascript seems to be another Datalog engine (in memory only) https://github.com/tonsky/datascript