Like Om but don't like LISP?

Hmm, I wonder how well this plays with something like [FKit](http://joshbassett.info/2014/take-your-code-to-the-next-level-with-fkit/)? Perfect together or do they just end up stepping on each other's toes? Maybe @nullobject has tried it? I'm keen to try out a few things with React and this looks good - immutable makes it awesome! I still need to give FKit a try, but would be interested in getting opinions before diving in.

So, @MostlyHarmlessD, if I understand this correctly this allows for re-rendering of individual react components without re-rendering the entire hierarchy? Does that translate directly to the DOM? My understanding of React is limited.

Hi! I've haven't looked at FKit before now, but as with regular usage of React, it is simply the presentation layer/interface. This means, your domain-logic, controllers, what have you, should not occur in the views but in a separate location in your code base. There is no reason why you couldn't use the functional "building blocks" and combinators from something like FKit. As for using the immutable objects from FKit as data structure for Omniscient, you could probably do it in some way, but Omniscient really encourages the usage of cursors to pass into components. This way you can separate the different components from one another without them having to know about each other. As far as I can see FKit doesn't have support for cursors/lenses (yet?).