react-cursor

SEEKING WORK - Philly or remote Full stack web apps, ReactJS expert, built two enterprise grade frontends in ReactJS (designed and led implementation - 50 to 100 pages of wireframes), two open source React libraries, multiple conference talks and workshops. Seeking long term ClojureScript work or short-medium term Javascript contract. (I am open to fixed price bids and project ownership, I have access to a small team who I have worked with before) https://github.com/dustingetz/react-cursor https://github.com/wingspan/wingspan-forms https://www.linkedin.com/in/dustingetz

Location: Philly Remote: Maybe Willing to relocate: Maybe Technologies: Clojure, ClojureScript Full stack web apps, ReactJS expert, built two enterprise grade frontends in ReactJS (designed and led implementation - 50 to 100 pages of wireframes), two open source React libraries, multiple conference talks and workshops. However I am no longer interested in working in javascript except on a contracting basis. https://github.com/dustingetz/react-cursor https://github.com/wingspan/wingspan-forms https://www.linkedin.com/in/dustingetz

if your state is { foo: ['a','b','c'] }, you can either do: cursor.refine('foo', 3).onChange('d') cursor.refine('foo').onChange(['a', 'b', 'c', 'd']) (indexes in a js array are the same as keys in a map) It is possible to implement `push` and other list/object ops that are exposed by React.addons.update, they have not been implemented yet because they make the interface more complicated. http://facebook.github.io/react/docs/update.html I opened an issue for discussion: https://github.com/dustingetz/react-cursor/issues/10

(Author here) I have added a short section to the readme describing how `react-cursor` differs from other, similar, libraries (e.g. Cortex). https://github.com/dustingetz/react-cursor#comparisons-to-si...

GitHub.com/dustingetz/react-cursor It supports o(1) shouldComponentUpdate My hn comment history has some discussion about it I'm on my phone now but if you email me I can give more info. I've used react-cursor in two enterprise grade apps in regulated industries and couldn't imagine using react without cursors (believe me I tried)

you are right, this is a sticky spot when using immutability from javascript - you can clone-and-mutate (I started here, but it quickly became a bottleneck in my app, and jr developers forget a lot leading to hard to find bugs) - you can use real persistent datastructures (Mori), but now you have added a cross cutting concern - which type of array is the one i'm working with right now? - you can use React.addons.update (I use this successfully, but you need to get used to a weird syntax) Om provides an abstraction over React state called Cursors which provides immutable updates to react state at any point in a state subtree. I ported this concept to javascript (implemented in terms of React.addons.update) and have used this successfully in two large scale enterprise applications for regulated industries and I know of one other company usi

https://github.com/wingspan/wingspan-forms https://github.com/dustingetz/react-cursor http://www.dustingetz.com/2014/02/18/react-dynamic-forms.htm...

I've done some research too - check out this implementation of cursors, it enables drop-in O(1) shouldComponentUpdate (like Om) and is compatible with rAF batching (like Om). We explored Mori for a bit too and ended up deciding Mori wasn't worth it. (Our app was big enough that we experienced pretty brutal performance without shouldComponentUpdate. Now our bottleneck is methods like Array.prototype.map over large lists in render, which Mori can't help with - we have to restructure our state away from lists and into trees to better take advantage of shouldComponentUpdate) https://github.com/dustingetz/react-cursor/blob/master/examp... https://github.com/dustingetz/react-cursor/blob/master/js/Cu... (It is backed by react.addons.update, it provides a mechanism like mori.assoc_in for immutable subtree updates, and it preserves reference equal