re-posh
relic
| re-posh | relic | |
|---|---|---|
| 2 | 13 | |
| 385 | 395 | |
| - | - | |
| 0.0 | 3.6 | |
| over 2 years ago | 5 months ago | |
| Clojure | Clojure | |
| MIT License | 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.
re-posh
- Use of Posh for frontend development?
-
ANN: relic - functional relational database and military grade anti-tar library.
Thanks for providing relic! Amazing tech for situated programs. You think relic is stable enough to integrate with re-frame like re-posh did? https://github.com/denistakeda/re-posh
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?
odoyle-rules - A rules engine for Clojure(Script)
walkable - A Clojure(script) SQL library for building APIs: Datomic® (GraphQL-ish) pull syntax, data driven configuration, dynamic filtering with relations in mind
posh - A luxuriously simple and powerful way to make front-ends with DataScript and Reagent in Clojure.
tigris - Tigris is an Open Source Serverless NoSQL Database and Search Platform.
electric - Local-first sync layer for web and mobile apps. Build reactive, realtime, local-first apps directly on Postgres.
hugsql - A Clojure library for embracing SQL
penpot - Penpot: The open-source design tool for design and code collaboration
hyhac - A HyperDex Haskell Client
datascript - Immutable database and Datalog query engine for Clojure, ClojureScript and JS
amazon-redshift-utils - Amazon Redshift Utils contains utilities, scripts and view which are useful in a Redshift environment