If your still fishing for ideas, this deserves more attention. https://www.reddit.com/r/Clojure/comments/il9oyd/oakesodoylerum_rules_engine_to_manage_all_the/?utm_medium=android_app&utm_source=share I think the ideas here are ripe for dissection and it's not clear where pulling them apart and putting them back together will lead at this stage.
Thanks for the suggestion.
Rules engines have always been intriguing to me, but I haven't used one in anger yet.
I feel like the generality can sometimes get in the way and I don't know when the right time is to accept that into my application.
When you say the ideas are ripe for dissection, do you mean rules engines themselves or the single state atom and how we try to make that work in our applications?
There are a couple things going on here. They feed into each other. Currently, front end web development is viewed as creating a Dom and attaching functions to it. Those might update the Dom itself. That's a very useful perspective. But we have it twice in that, to some extent, we can view the rendered html. it's also valid to see the applications as a series of functions (rules in this case) that update the Dom. That's what this does. That's another perspective. Ideally, I think both these options should be available and we should be able to toggle between them Difficult problems are usually simple ones that your to far away from to see the solution. I don't think it will change the world, but it seems like a very nice to have.
It's been a busy few weeks, but today is a new episode on partition-by
and group-by
: https://clojuredesign.club/episode/083-sift-sans-sort/
Have a great weekend.