In a recent London Clojurians talk, the author Leo Noel explained Electric can be thought of as a frontend for Missionary. Rama is by a different team (RPL), but agreed, their philosophies are similar.
Oh they updated the docs! Then I'll have to give it another look. I tried to make a simple subscription/memoization setup but I couldn't figure it out. They have a lot of keywords/terms (task/flow/etc.) that a bit hard to understand.. and even when you make sense of them isolation it was still a bit unclear how to compose them properly. The resulting code had to specify a lot of things and was more verbose than I had hoped for
I'll be honest, part of the problem is I don't work in the web space. So I don't care for (or completely understand) the things they're looking to solve (ex: server/client sync issues). I just want to have simpler state-management and have changes propagate across my program in a way that makes my life easier :) (think like a "notebook" where you update values and everything gets reevaluated where-needed)
The tutorials are fairly accessible: https://cljdoc.org/d/missionary/missionary/b.33/doc/readme/t...
In a recent London Clojurians talk, the author Leo Noel explained Electric can be thought of as a frontend for Missionary. Rama is by a different team (RPL), but agreed, their philosophies are similar.