On: Why We Use Om, and Why We’re Excited for Om Next

[jlongster]

I don't think it's that's simple. It's not that it works better for hugely complex apps. It just works better for certain kinds of apps, even if they are small. The project I'm working on is small, but Om Next is far better suited to it (the complexity of using Redux+Redux/etc on it would be far greater).

The question is, are the majority of apps better suited for a tree-based state or a queryable graph? I'm not sure, but it's at least even.

I've heard Elm is working on something similar, so I wouldn't be surprised if that happens.

[slorber → jlongster]

Is the same data displayed into multiple branches of the tree? :)

[jlongster → slorber]

You mean the component tree? Sure, it can mixed in whatever way the component tree wants it.