Also I'd give up Mocha, Chai & Sinon for tape, which is way simpler and more than enough:
https://medium.com/javascript-scene/why-i-use-tape-instead-o...
Also I'd give up Mocha, Chai & Sinon for tape, which is way simpler and more than enough:
https://medium.com/javascript-scene/why-i-use-tape-instead-o...
That's not to say that you should necessarily use Immutable.js; if you don't understand the use case where structural sharing in persistent immutable data structures is useful and require it for your application then you should probably just leave this tool on the shelf.
However, if, for example, you are maintaining maps containing many items which are updated frequently, then you may benefit from the time and space complexity of structurally shared maps (Immutable.js) rather than creating a full copy on each mutation (plain JS objects).
No need to insinuate that I don't understand. I've used it extensively in production and I think most code-bases are better off without Immutable.
> However, if, for example, you are maintaining maps containing many items which are updated frequently, then you may benefit from the time and space complexity of structurally shared maps (Immutable.js) rather than creating a full copy on each mutation (plain JS objects).
It was exactly this situation, maintaining maps with thousands of GeoJSON features and working on these items, where I found Immutable to fall short. The parsing/building of the data-structure alone took, If I recall correctly, about 50 times longer than with normal JS-objects.
[0]: https://www.reddit.com/r/javascript/comments/4rcqpx/dan_abra...
[1]: https://github.com/markerikson/react-redux-links/blob/master...