datascript
re-frame
Our great sponsors
datascript | re-frame | |
---|---|---|
24 | 23 | |
5,352 | 5,376 | |
- | 0.2% | |
7.7 | 9.1 | |
7 days ago | about 1 month ago | |
Clojure | Clojure | |
Eclipse Public License 1.0 | 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.
datascript
-
Datalog in 100 lines of JavaScript (2022)
Hi pests, I don't think the criticism in the comments gives a full picture.
I wrote about a particular flavor of datalog, in common use today. [1] [2]. The earliest representation I know, which matches the syntax of my essay, was in SICP [3]
There's another, more academic form of datalog, which looks a lot more like prolog. Both have lots of similarities: both systems have a set of facts and rules. Both systems have can take a partially filled fact or rule, and find all matching facts. The more academic flavors of Datalog are useful for general logic, and particularly powerful for recursive questions. The variant I showed is more tailed for database queries.
[1] https://github.com/tonsky/datascript
-
XTDB on Mobile Possible?
There is also datascript as a similar option.
- FoundationDB: A Distributed Key-Value Store
-
wotbrew/relic: FRP for Clojure(Script)
What's the use case for relic? Sounds similar to https://github.com/tonsky/datascript ?
- Introduction to Datalog
- Clojure Turns 15 panel discussion video
-
Show HN: Cozo – new Graph DB with Datalog, embedded like SQLite, written in Rust
This look nice !
Datascript seems to be another Datalog engine (in memory only)
https://github.com/tonsky/datascript
-
Ergonomic inline SQL as a Python library
Inspired by past work: LINQ, inline-python, crepe, DataScript, Riffle.
-
Working with large maps
An in-memory database like Datascript may be worth looking into. Otherwise you could take an indexing approach: put all the data into one big map indexed by some unique key, and have a bunch of supplementary indexes that are updated on insertion.
- Obsidian Dataview: Turn Obsidian Vault into a database which you can query from
re-frame
-
Goodbye, Clean Code
This article always reminds me of this excerpt from re-frame’s docs [0]:
> Now, you think and design abstractly for a living, and that repetition will feel uncomfortable. It will call to you like a Siren: "refaaaaactoooor meeeee". "Maaaake it DRYYYY". So here's my tip: tie yourself to the mast and sail on. That repetition is good. It is serving a purpose. Just sail on.
[0]: https://github.com/day8/re-frame/blob/master/docs/correcting...
-
A History of Clojure (2020) [pdf]
* Single-Page App: shadow-cljs for the build concerns (https://github.com/thheller/shadow-cljs), Reagent with Re-frame for complex/large app (https://reagent-project.github.io and https://github.com/day8/re-frame). Even if we now prefer using HTMX (https://htmx.org) and server-side rendering (Hiccup way of manipulating HTML is just amazing, https://github.com/weavejester/hiccup).
-
Is there an open source project focused on ClojureScript, React, Reagent?
Big and/or complete projects that use re-frame The main list: https://github.com/day8/re-frame/blob/master/docs/External-Resources.md
-
Reflet introduces descriptions: a new kind of polymorphic query
Reflet is a set of tools for building Re-frame + React based web apps with graph and non-graph data models. This includes:
-
Were React Hooks a Mistake?
https://github.com/day8/re-frame
Notably the author of re-frame has been weary of hooks.
I think that’s for a good reason. The approach in re frame feels like the best way to manage state so far for a react based app. Everything that changes state flows through an event. State can only be observed through subscriptions. Side effects are isolated to their own type of event. Debugging and testing are so straight forward with these concepts.
Redux got close but it has two problems in my mind. Like hooks, it encapsulates for no good reason. Put the state in one thing that you can observe holistically before and after pure events. It also has too much boiler plate.
-
Clojure Turns 15 panel discussion video
The cljs stack I hear about a lot (and use) is ShadowCLJS with reagent (https://reagent-project.github.io/) and re-frame (https://day8.github.io/re-frame/). ShadowCLJS is more of a build tool, but is really well documented and easy to use. Reagent is basically react but a simpler API, and re-frame is a layer on top of that provides data subscriptions and event-handlers to manage app state. It's overkill for some apps but I find it's actually super easy to work with and not as much complexity as I thought.
For backend there is luminus (https://luminusweb.com/) or Kit (https://kit-clj.github.io/). They are basically project templates that wire together a ton of popular solutions for various things - database access, migrations, security, html templating, etc. Also includes frontend frameworks like re-frame if you want.
-
Reflet: building Re-frame + React based web apps with graph and non-graph data models
Reflet aims to be a natural progression on top of Re-frame to support complex, data driven requirements. In that sense, it is both easy to learn, but powerful. You could say it's sort of like Re-frame++ (or Fulcro for Re-frame). Its main design goals are:
-
Killing mutants to improve your tests
At my current client we're working on having a frontend architecture for writing SPAs in JavaScript similar to re-frame's one: an event-driven bus with effects and coeffects for state management[1] (commands) and subscriptions using reselect's selectors (queries).
-
Giving new life to existing Om legacy SPAs with re-om
Some of us had worked with effects and coeffects before while developing SPAs with re-frame and had experienced how good it is. After working with re-frame, when you come to horizon, you realize how a good architecture can make a dramatic difference in clarity, testability, understandability and easiness of change.
-
what componies uses Clojure, and what componies deceased the use of other languages after additions of Clojure, for example Dropbox decrease the use of python after addition of Go programming language, are there any similar story with Clojure?
https://youtu.be/geeK1-jjlhY (talk about an initial prototype with re-frame and the decision to do a rewrite in Clojure)
What are some alternatives?
asami - A graph store for Clojure and ClojureScript
reagent - A minimalistic ClojureScript interface to React.js
datahike - A durable Datalog implementation adaptable for distribution.
fulcro-rad-demo - A demo for Fulcro RAD using either SQL or Datomic databases.
datalevin - A simple, fast and versatile Datalog database
Recoil - Recoil is an experimental state management library for React apps. It provides several capabilities that are difficult to achieve with React alone, while being compatible with the newest features of React.
10000-markdown-files - 10,000 markdown files. Useful for stress testing note-taking tools.
Elm - Compiler for Elm, a functional language for reliable webapps.
xtdb - An immutable database for application development and time-travel data compliance, with SQL and XTQL. Developed by @juxt
reitit - A fast data-driven routing library for Clojure/Script
Apache AGE - Graph database optimized for fast analysis and real-time data processing. It is provided as an extension to PostgreSQL. [Moved to: https://github.com/apache/age]
django-extensions - This is a repository for collecting global custom management extensions for the Django Framework.