todomvc

This sounds like a case of simple, not easy: http://www.infoq.com/presentations/Simple-Made-Easy You could add a timestamp to each todo with two changes: https://github.com/swannodette/todomvc/blob/gh-pages/labs/ar... (defn handle-new-todo-keydown [e {:keys [todos] :as app} owner] ... (om/update! app [:todos] conj {:id (guid) :title (.-value new-field) :created-at (js/Date.) ;; <-- add this line :completed false :order (count todos)}) ...) https://github.com/swannodette/todomvc/blob/gh-pages/labs/ar... (defn todo-item [{:keys [id title editing completed] :as todo} {:keys [comm]}] ... ;; change this line (dom/label #js {:onDoubleClick #(handle-edit % todo m)} (str (:title todo) (:created-at todo))) ...)

It may be because I'm not familiar with ClojureScript's syntax, but the whole sample application code seems like a real mess to me. It's full of boilerplate code and it is happily mixing application logic with DOM rendering. [1] Compare this with an alternative JS MVC framework (like, say, Knockout.js) and another modern "javascript-compatible" language (like, say, TypeScript), and see for yourself. [2] While I didn't run any benchmarks, it's safe to assume the Om demo is faster. However which sample do you think is easier to write, test and maintain? If "The Future of JavaScript MVC Frameworks" is supposed to look like the Om sample, sorry but I'll pass. [1]: https://github.com/swannodette/todomvc/tree/gh-pages/labs/ar... [2]: https://github.com/jpatte/TodoMvc-Knockout.ts

Om looks very interesting and seems to handle exactly what I've been looking for. We have reactive widgets, which is great for making changes in the data automatically update the UI. But the hard part is closing the loop: how does the widget communicate back to the data about changes? It would be interesting if we had a zipper-like abstraction, so that the widget gets handed both its data and a function to call when it wants to change just its data. Then that function is smart enough to go find the right place in the big data structure to go do the replace. Edit: Ok, I now see how the Om todo example is handling update, and it's really cool. It creates a set of channels that encapsulate the knowledge of how to handle each type of change to a todo [0]. That gets passed in to the todo widget as "chans" and the widget sends messages to it in