Om Next
summary
Om Next presents a concrete UI architecture: components supply Datomic-like pull queries collocated with their code, a parser evaluates reads and mutations both client- and server-side, and responses normalize into a graph using two-element idents so identical entities stay in sync. Mutations support tempid to real id resolution and optimistic local commits; server returns which keys to reread. Multiple remotes enable standard HTTP caching, client-only state and streaming are supported, testing uses generative test.check scenarios, and the implementation is near beta with documentation pending.
AI-written summary · about
chapters (14)
- 0:00The problem with UI
- 2:40Om Next core principles
- 5:31Precise read requests
- 9:22Query composition
- 12:52Parsing queries
- 15:51Handling mutations
- 18:55Identity and temp IDs
- 20:42Client state and normalization
- 24:37Optimistic updates
- 25:08Testing with property checks
- 31:47Recursive UI patterns
- 32:35Caching strategies
- 35:27System customization
- 36:38Project roadmap and conclusion
related talks
34mWhat's Next? Exploring the future of React
21mHow Next.js is delivering React’s vision for the future
34mOm nom nom nom
22mRedux, Re-frame, Relay, Om/next, oh my!
23mOptimistic UI updates with Apollo Client and React
38mComposable Healthcare
43mGraphQL in the Era of Server Components
39mImmutable User Interfaces