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

Post by dwwoelfel » Thu, Jan 21, 2016, 11:12 PM UTC

amelius wrote: post #50

> Om’s creator, David Nolen, likes to show off how easy this makes it to implement undo: just remember a of list old states, and you can reset! the state atom to any of them at any time. How does that work if multiple users are collaborating on the same state simultaneously?

Post by [deleted] » Thu, Jan 21, 2016, 11:14 PM UTC

dwwoelfel wrote: post #51

amelius wrote: post #50

> Om’s creator, David Nolen, likes to show off how easy this makes it to implement undo: just remember a of list old states, and you can reset! the state atom to any of them at any time. How does that work if multiple users are collaborating on the same state simultaneously?

> How does that work if multiple users are collaborating on the same state simultaneously? The state they're talking about here is local to the client--it's stored in memory on the browser. One one user can use it at a time.

Post by dwwoelfel » Thu, Jan 21, 2016, 11:29 PM UTC

enobrev wrote: post #54

dwwoelfel wrote: post #48

I was the main author of Circle's frontend (the code is open-source: https://github.com/circleci/frontend ). I went on to build Precursor ( https://precursorapp.com ), which uses Datascript ( https://github.com/tonsky/datascript ) to accomplish a lot of the things that Om Next promises. If you haven't tried Datascript, you should really take a look! It does require a bit of work to make datascript transactions trigge…

There's a typo in your datascript url (s/k are switched). Here's the corrected one: https://github.com/tonsky/datascript

Post by faceyspacey » Fri, Jan 22, 2016, 12:26 AM UTC

Post by tonyhb » Fri, Jan 22, 2016, 5:05 AM UTC