Clojurians Log v2

@nbtheduke strong +1 on the kanren paper, it captures the essence of the matter in clear prose and very little code. There’s also the wonderfully succinct micro kanren http://webyrd.net/scheme-2013/papers/HemannMuKanren2013.pdf Print the papers out and pretend they’re books 🙂

uK paper is a gem, but reading mK first makes it that much more glorious Consider the uK a cogito hazard. Sure, you'll say, I can implement it myself, short adventure, I'm sure there will be no side effects

Case in point, I got here because of Kanren

datalevin 1.0 will comes with a book at http://datalevin.org

if you are inpatient, the unfinished book is already at https://github.com/datalevin/docs/tree/main/resources/docs

oh wow that's quite far along. like i said, i learn best from physical books so maybe i can get that printed when it's finished

yes, the plan is to have a print book.

I bet @jackrusher can recommend a few

I was more involved in older flavors of datalog, which have a more PROLOG-y syntax. The semantics are very similar, but the notation is probably a barrier for someone who just wants to learn about using Datomic. @daveliepmann might have some ideas, though, as he’s working with the Datomic team these days…

i'd take a prolog book too, because i expect conceptually they're similar

i'm mostly trying to reframe how i think about databases and storage after 20 years of sql

You might want to go through the datalog engine from scratch blog posts

Start here https://buttondown.com/tensegritics-curiosities/archive/writing-the-worst-datalog-ever-in-26loc/

Another prism to look at this through is minikanren, the thesis is very readable. By the time you reach cKanren and alphaKanren there are very few surprises left in datalog implementations

i love books which is why i was asking about books but i'll definitely read that blog series

The blog series might be considered a non formal intro. I also prefer books. And papers. They often contain the lion's share of the original theory and work. This is the mk thesis https://www.proquest.com/docview/304903505

thank you!

Welcome 😊 I think the two major conceptual hurdles are: Indexing, etc is incidental. It is an optimization for more efficient queries. Storage is just a persistence layer. Depending on what you need in memory and your access patterns you'll choose the appropriate storage.

Same here, I read these 3, top 3, but it's a long time ago now so this list might be way better now • Professional Clojure Jeremy Anderson Michael Gaare Justin Holguín Nick Bailey Timothy Pratley • Clojure Cookbook by Luke VanderHart & Ryan Neufeld • Learning ClojureScript by W. Davis Jarvis, Rafik Naccache, Allen Rohner