relic

Also in Clojure, and reactive, and relational: https://github.com/wotbrew/relic > Functional relational programming for Clojure(Script).

Fwiw my colleague is the author of https://github.com/wotbrew/relic and he started working on Incremental View Maintenance ~purely because he wants to build a simpler rogue-like :)

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 :)

I came across this after seeing relic[0] submitted the other day and thought it was pretty interesting. I've been into CRDTs for a while and have started wondering about generic mechanisms for distributed data. This lead me to read a lot more about the Relational Model of data and eventually to the Event Calculus. What's interesting to me is that these things end up feeling a lot like CRDTs[1] or Event Sourcing. I haven't quite finished pulling on these threads but the relic link was a timely read considering! I really liked the first half of this paper and the Authors categorization of complexity. However the second half fell a bit short for me. It seems they made the same mistake as many other people (SQL != Relational) and their idea of Feeders and Observers seems a bit more like an escape hatch than an elegant method for interfacing w

Ahhh... a fellow traveller on the road. I have been hacking on a Clojure/Script library (https://github.com/wotbrew/relic) to experiment with exactly this kind of thing. / PLUG For most problems I encounter I want to focus on the data and its relationships. I cannot help feeling like programming languages and idioms have me deal with too much 'mechanism', the machine like structures and forms that are mostly incidental to the data domains I work in, and are entirely about performance, layout, access pattern etc - when a machine could do an ok job of making those decisions for me until optimisation becomes important.