| pararules | spork | |
|---|---|---|
| 1 | 1 | |
| 135 | 73 | |
| 0.7% | - | |
| 3.0 | 7.2 | |
| 7 months ago | about 2 months ago | |
| Nim | Clojure | |
| The Unlicense | Eclipse Public License 1.0 |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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.
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.
pararules
Posts with mentions or reviews of pararules.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2021-02-10.
-
O'Doyle Rules - a Clojure rules engine for the best of us
The algorithm is the same but yes it's mutable. Maybe the most interesting difference that affects performance is that in nim i can generate a special stack-allocated type to store your matches internally. It is a sum type, which nim calls an object variant, that has a "branch" for each rule. Unsurprisingly this was a huge perf improvement over using hash tables. Generating types with a macro is some wild stuff :D
spork
Posts with mentions or reviews of spork.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2021-02-10.
-
O'Doyle Rules - a Clojure rules engine for the best of us
As far as code, my implementation focuses on the functional approach. There's a stress test in the testing ns, of which the behavior-related stuff looks like this (I re-ordered it for presentation purposes, I typically define this stuff in a clojure friendly way, building "up" more complex behaviors as you go down the through the source, this is "top down" for visual purposes):
What are some alternatives?
When comparing pararules and spork you can also consider the following projects:
odoyle-rules - A rules engine for Clojure(Script)
odoyle-rum-todo
paranim_examples