typedclojure VS missionary

...and Typed Racket is a really powerful type system (see refinement types[4]). So, I thought it's just a matter of time for Clojure to get to that level of power and support. It should be much easier to do this to Clojure than to Ruby, given that you have a working example of how to do it well. So I'm really surprised Clojure isn't gradually typed by now, with most of the code being annotated and type-checked at compile time.

[1] https://github.com/clojure/core.typed

[2] https://github.com/typedclojure/typedclojure

[3] https://github.com/typedclojure/typedclojure/blob/main/examp...

[4] https://docs.racket-lang.org/ts-reference/Experimental_Featu...

you mean with typedclojure?

I'm talking about the fact that a particular dynamic language has it, whether some people use it or not is moot. https://github.com/typedclojure/typedclojure is the successor to the erstwhile popular core.typed library, and normal Clojure itself allows for type annotations to (potentially) help improve performance.

Seeing that there is a need for type checking in Clojure. Has anyone used https://github.com/typedclojure/typedclojure in production?

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