Ramda vs Immutable

Mostly just a comment. We’ve switched in our este based project from ImmutableJS to Ramda. We’ve had issue both from a performance perspective and usage perspective with a lot of going back and forth between POJO and Immutable. We’ve found that using Ramda, which provides pretty much the same functionality as ImmutableJS, solves most of these issues.

Map.setIn => R.assocPath Map.getIn => R.path Map.deleteIn => R.dissocPath

[ronag]

Another reason we switched is that we prefer to have our React components as regular dumb components without any “magic” from Immutable. Spread operators work, PropTypes work, destructuring works and also easier for new members to the project to get started with the React component development.

[ronag]

@XeeD: Hm, yes, you are correct about destructing. However, we still need to do <Foo {...foo.toObject()}/>

Reselect allows you to pick and convert the objects before they enter the component.

Yes, we did this as well.

I speak from our experience, we have about 20 developers working with Este based stacks and we do not feel any pain working with Immutable, in fact it quite the opposite.

Well, we did start out with Immutable and yes we used react-immutable-proptypes. We couldn’t get it to work technically due to performance issues. After switching to Ramda we noticed that we could remove a lot of “workaround stuff” (immutable-proptypes, toJS, fromJS, toObject, redux-devtools issues and performance etc…). However, we are only 3 devs.

Not saying that Immutable is bad, just that we found Ramda much simpler, and performant for our specific application. Just sharing our experience.