@sova I’m testing if can get the benefits (as far as I understand them) of om.next in rum. So I’m now looking at the querying part of om.next. It seems I can copy the query parser and some other namespaces. I have to reimplement the indexer, i think, as it is highly coupled to om.next. I cannot promise that I will ever finish it, so please don’t hold your breath. It always helps though if there are people with om.next experience that also know how rum works

@sova I was just pointed to https://github.com/roman01la/scrum it is almost what i want i believe

I was just about to comment about global state, but getting rid of it is mentioned in the roadmap

Not sure I really like the subscribe/dispatch model. I guess it can have better performance due to how react works?

And yes, I know that's how re-frame works.

What do you see as a downside of the subscribe/dispatch model? As for the subscribe part, isn’t this how everything works in the async world?

Aren't UIs pretty synchronous when you think about it? Server requests are async, but you don't need an event model for those if you don't want to, you can use callbacks too.

https://metametadata.github.io/carry/

Carry has a model that doesn't rely on dispatches

I'm not saying it's necessarily better, just pointing out it's difference 🙂

I'd also like to explicitly give my components their parameters, and not have them depend on outside state

Yes I agree. I was maybe generalising too much. I didn’t know about Carry, thanks for the link.

https://github.com/tatut/tuck this is another good one. Doesn't have much docs though

Actions are records

and what's unique is that the components can have their own state atoms, which means it's easier to start using in the middle of a project

I do think having one state IS better, but if you already have thousands of lines of code, it's hard to move to that model 🙂

Hi! I'm playing around with alumbra (a Clojure GraphQL library) and having a lot of fun. Has someone used rum with GraphQL or built any mixins for use with GraphQL?

Is alumbra for the front-end or backend?

@mruzekw It's for the backend

I thought so.

The only frontend graphql tool I know of is https://github.com/retro/graphql-builder