missionary VS electric

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.

I wonder if anyone can compare these to missionary?

related: https://github.com/leonoel/missionary

- https://github.com/leonoel/missionary

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

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.

Process supervision is what Missionary implements: https://github.com/leonoel/missionary

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

The cleanest way to handle the backend and frontend charade I've seen until now is using https://github.com/hyperfiddle/electric which is a clojure DSL on top of react

Opa was ahead of its time by at least 10 years. Have you seen Electric Clojure [0]?

[0] https://github.com/hyperfiddle/electric

Scala's ZIO/ZLayer is a great implementation of this idea where the monadic types are visible to userland DSL. Electric Clojure (which I lead) is a Clojure implementation of similar ideas (specialized to web development) where the types are concealed, "just write Clojure". In practice with Electric, we are building really complex/dynamic abstractions (think pure functional app-builder and highly concurrent UI) and we haven't even felt a need to implement multimethods yet. https://github.com/hyperfiddle/electric

I'd expect your auth stuff to mostly just work with some minor jiggling of the middlewares. We have a few out of the box approaches to routing, the tutorials app uses hyperfiddle.router which is an experimental composable router (may be a bit hard to use), the easiest starting point would be a simple goog.history integration. Someone posted a retit integration in the slack iirc. And you can of course roll your own.

Built with Electric Clojure and Missionary! https://github.com/hyperfiddle/electric