re: I'm a professional React developer, and these are the npm packages I use the most often. VIEW POST

TOP OF THREAD FULL DISCUSSION
re: Just wondering on how you manage immutable data throughout your applications, where do you start and stop using them and fallback to native JS type...
 

Hi Ben, thanks for your comment!

Just wondering on how you manage immutable data throughout your applications, where do you start and stop using them and fallback to native JS types?

The main two benefits to using Immutable are the performance benefits you get from manipulating data, and also giving your code a certain "structure" to it. However, you can only benefit from Immutable if you keep the data immutable - if at some point you run .toJS() on your data set, you're essentially losing any performance gains you get. This is why I only use Immutable in very specific use cases, namely for managing data within certain reusable components (I use it on a full-blown image uploader and also a file explorer at the moment). If you're doing it within Redux chances are you can save a couple bytes, reduce confusion and gain some performance from removing it :)

Second question - Immutable seems to be stuck at the next release candidate and appears not to be maintained anymore.

Highly doubt that that's the case. Immutable is maintained by Facebook, and also used by Facebook in its DraftJS rich text editor... so highly doubt it's going anywhere anytime soon.

 

Actually, the last commit was February 14, 2019 ( github.com/immutable-js/immutable-... ). And the 4.0 release has been a release candidate for 2 years. Additionally, you can read through this GH issue on their site: github.com/immutable-js/immutable-...

Interesting. Thanks for that Andy!

 

Hey. That makes sense, thanks for the reply! Good to hear that Immutable will be around for a while.

code of conduct - report abuse