←back to thread

Optimizing Datalog for the GPU

(danglingpointers.substack.com)
106 points blakepelton | 1 comments | 04 Nov 25 14:31 UTC | HN request time: 0.209s | source
Show context
haolez ◴[04 Nov 25 16:05 UTC] No.45812510[source]▶
On a side note, what tools that leverage Datalog are in use by the HN crowd?

I know that Datomic[0] is very popular. I've also been playing with Clingo[1] lately.

[0] https://www.datomic.com/

[1] https://potassco.org/clingo/

replies(4): >>45812637 #>>45812964 #>>45816960 #>>45817369 #
embedding-shape ◴[04 Nov 25 16:15 UTC] No.45812637[source]▶
I have some local-first/client-side applications using datascript in ClojureScript. Used datahike (FOSS Datomic alternative) some times on the backend too, but mostly tend to use XTDB nowadays, which used to have a Datalog API but I think they removed in favor of SQL-like way instead, which was kind of a shame.
replies(1): >>45813761 #
manoDev ◴[04 Nov 25 17:46 UTC] No.45813761[source]▶
I guess SQL is a requirement if they want to market their technology to normies.
replies(1): >>45815744 #
zozbot234 ◴[04 Nov 25 20:51 UTC] No.45815744[source]▶
SQL can express Datalog-like queries rather easily using recursive CTE's, and even more so via the recently-added Property Graph Query syntax.
replies(1): >>45817304 #
1. jitl ◴[04 Nov 25 23:52 UTC] No.45817304[source]▶
recursive CTEs suck usability-wise compared to the usual Datalog horn clause syntax. I won't speak to usability of the "datomic" kind of datalog though, that thing I haven't been able to wrap my head around.