odoyle-rules
relic
odoyle-rules | relic | |
---|---|---|
10 | 13 | |
517 | 395 | |
- | - | |
6.2 | 3.6 | |
7 months ago | 5 months ago | |
Clojure | Clojure | |
The Unlicense | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
odoyle-rules
-
Use of Posh for frontend development?
If you're going down this route I'd second the recommendation for O'Doyle Rules. (Haven't used it since I switched away from SPAs altogether, but when I was investigating stuff in that space, O'Doyle appeared to be taking the "correct approach" from what I could tell.)
-
[Blog] The Web Before Teatime
That's what this tiny library does https://github.com/oakes/odoyle-rules
- [ANN] odoyle-rules 1.0.0
-
Ideas for DataScript 2
Reactive updates is the big one, in my opinion. DataScript is a triumph and arguably is the reason why so many note-taking tools (Roam, Athens, Logseq, etc) are written in Clojure. But there are so many cases where it would be nice to react when some set of entities is changed.
I think what we need is to figure out how to combine DataScript with a rules engine. I'm wrote a rules engine and made a writeup that compares the two together: "Using O'Doyle Rules as a poor man's DataScript" https://github.com/oakes/odoyle-rules/blob/master/bench-src/...
Subscribing to individual entities is nice but with a rules engine you have so much more fine-grained control over your reactions. And with the RETE algorithm this can be done efficiently. Most libraries in this space just ignore it and make their own ad-hoc solution -- an informally-specified, bug-ridden, slow implementation of half of a rules engine.
- UIs Are Streaming Dags
-
Datalog for HTTP APIs
Odoyle-rules lets you write rules (forwards chaining) engine that you can run on client and server. There are a couple ways you can twist that idea to achieve a more unified system.
-
Next Web
I suspect it'd be too much of a mismatch to be useful, but i haven't thought about it enough. I think a more promising idea is to try implementing a database with o'doyle. I wrote about my first attempt here: Using O'Doyle Rules as a poor man's DataScript Right now it would be too inefficient for large data sets because it has to constantly rebuild its index but i think with some small changes i could improve that and basically turn o'doyle into a tool for creating databases that come with reactivity for free.
-
O'Doyle Rules - a Clojure rules engine for the best of us
No doubt there's a runtime cost in joining the facts together, so naturally a system that lumps facts together into records (like clara) will have to do fewer joins, and should be faster. I figured out that i could at least deduplicate my joins with derived facts as i explained here, which ended up being a really big perf boost. But there's still a tradeoff, and one where almost everyone should favor flexibility, i think.
relic
-
FoundationDB: A Distributed Key-Value Store
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
-
Use of Posh for frontend development?
As an alternative to datascript you might be interested to try https://github.com/wotbrew/relic which does materialized views of queries with incremental maintenance.
-
Out of the Tar Pit (2006) [pdf]
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 with the outside would.
[0] https://github.com/wotbrew/relic
- Relic: Functional relational programming for Clojure(Script)
- Relic: Functional relational programming for Clojure(Script).
- Functional relational programming model in Clojure(Script)
- wotbrew/relic: FRP for Clojure(Script)
-
ANN: relic - functional relational database and military grade anti-tar library.
I have recently cut the first alpha release of relic that I'm happy to share: https://github.com/wotbrew/relic.
What are some alternatives?
pararules - A Nim rules engine
walkable - A Clojure(script) SQL library for building APIs: DatomicĀ® (GraphQL-ish) pull syntax, data driven configuration, dynamic filtering with relations in mind
paranim_examples
tigris - Tigris is an Open Source Serverless NoSQL Database and Search Platform.
asami - A flexible graph store, written in Clojure
hugsql - A Clojure library for embracing SQL
posh - A luxuriously simple and powerful way to make front-ends with DataScript and Reagent in Clojure.
penpot - Penpot: The open-source design tool for design and code collaboration
spork - Spoon's Operations Research Kit
hyhac - A HyperDex Haskell Client
missionary - A functional effect and streaming system for Clojure/Script
datascript - Immutable database and Datalog query engine for Clojure, ClojureScript and JS