This compares briefly how they differ in managing their app state. https://youtu.be/-jwQ3sGoiXg (Om.next vs reframe)

awesome thanks!

That was a great video thanks. I think the take away from that and skimming the docs is that Fulcro looks to help at a systems level (db -> UI). Is that right? Are there other general ways of comparing them?

I’m fascinated by fulcro and by hyperfiddle. Im excited that i’m not the only one that things we can make systems more declarative and that using rest calls is a major source of the mismatch. I do assume, that given i have only skimmed the surface, there is an ocean of reasons why things are they way they are though 🙂

At my previous job I had worked on a re-frame app and thought it was fairly intuitive to understand, although I’m unsure how well it handles complexity as the app grows (that app I worked on was fairly small). I can’t speak for everyone but when I first started out with om.next it definitely took longer for things to click. The learning curve is much higher, but to me it seems to handle scale/complexity really well and I find it extremely gratifying to work with. I’m still new to fulcro but from what I can tell, it seems to chop the learning curve in half. If I were starting from scratch, I’d choose fulcro for sure 🙂

@U0DJ4T5U1 there’s this book, in case you haven’t seen it http://book.fulcrologic.com

also, fulcro no longer depends on Om.next

Om next was forked, absorbed, and modified in the last major version

also the devcard exercises are really great for getting over the learning curve

So, since this is a general question of architecture, and how it differs, I want to chime in with as minimal a statement as I can make: Fulcro has a very tightly integrated data, query, response architecture that permeates the entire stack. Most others have a story about how to write UI, but they don’t really take a stand on how you do communication, how that integrates with a data model, or why you should even care. Fulcro attempts (and IMO largely succeeds) to take a stand on these that doesn’t sacrifice the flexibility you need, but focuses you to a solution that encourages clear thought and minimal complexity around meeting those needs. What appears as added complexity and overhead of queries, idents, and normalized databases pay off with dividends as soon as you get beyond the trivial app and start needing data to flow in and out of your system.

Thanks for sharing Tony! That makes sense to me

I’m doing a presentation of fulcro at work on Friday, so this is all very relevant 👍

@U3CN1DLJ1 can you share it with me? I want to do the same thing

Yeah, once I have it created I will!

Glad to proofread and comment