missionary
odoyle-rules
missionary | odoyle-rules | |
---|---|---|
24 | 10 | |
605 | 514 | |
- | - | |
7.8 | 6.2 | |
13 days ago | 7 months ago | |
Clojure | Clojure | |
Eclipse Public License 2.0 | The Unlicense |
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.
missionary
- Humble Chronicles: Managing State with Signals
- Is there a reframe/cljfx-like subscription/memoization-context library available?
-
[Blog] The Web Before Teatime
I think the reactive query problem is more of a spectrum of tradeoffs, there's a middle ground between "full page refresh on nav" and "refresh all query subscriptions per user per tx". Truly realtime things like chat come from a streaming event source (not a database) and even in a chat app, most of the information coordinates on a page is slow moving. So really this is about regaining control over concurrent data flow so we can sample different views at different speeds. See technologies like https://github.com/leonoel/missionary.
-
Comparison of manifold and clojure.core.async
I wonder if anyone can compare these to missionary?
-
Is there a general IO library built to work with core.async?
related: https://github.com/leonoel/missionary
-
Structuring Clojure Applications
- https://github.com/leonoel/missionary
-
IO/async monad without the indirect monadic style: Possible? needed?
https://github.com/leonoel/missionary has excellent syntax, it uses a macro to extend regular clojure syntax with monadic join operator – basically turning clojure sexprs into do-notation
-
What are the essential libraries to learn for web dev
I recommend having a look at missionary - it is probably the most essential library in our application. But it depends on what type of application you are building.
-
UIs are streaming DAGs
Process supervision is what Missionary implements: https://github.com/leonoel/missionary
-
Questions about Rich Hickey's comments on static types
Agree - mostly the opinions are just dated, in 2005-2012 the pure FP world (especially Scala) was in rough shape but then in 2018 Maybe Not (the really controversial talk about "Maybe Sheep") it didn't seem like he had taken the time to understand haskell. I would love to see how his opinions have evolved since then, in the 2017 interview with fogus he said "If I had more free time, I’d spend it with Haskell". Haskell has especially come a long way in 2018-2022 with the popularization of functional effect systems which are extraordinarily powerful; for example https://github.com/leonoel/missionary (2020-2022) is the best Clojure effect system and is a leap forward over core.async (2013), but that 9 year difference is a lifetime in CS
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.
What are some alternatives?
awesome-clojure - A curated list of awesome Clojure libraries and resources. Inspired by awesome-... stuff
pararules - A Nim rules engine
honeysql - Turn Clojure data structures into SQL
paranim_examples
react-grid-layout - A draggable and resizable grid layout with responsive breakpoints, for React.
asami - A flexible graph store, written in Clojure
reitit - A fast data-driven routing library for Clojure/Script
posh - A luxuriously simple and powerful way to make front-ends with DataScript and Reagent in Clojure.
malli - High-performance data-driven data specification library for Clojure/Script.
spork - Spoon's Operations Research Kit
manifold - A compatibility layer for event-driven abstractions
relic - Functional relational programming for Clojure(Script).