Thanks for the write up.
Pratik Karnawat

No problem!

It’s less the paradigm itself than the library you choose to use. With moize, for example, using the default setup with moize.react will keep a cache of every element generated by React.createElement, because internally it stores an uncapped cache of previous responses. When the number of possible values passed is finite, this is okay as the cache can only possibly grow to the size of the number of possibilities, however the more varietal the props the larger the number of possible cache entries, and therefore the larger the potential memory footprint. With React elements especially, this can get costly with 10, 50, 100 elements stored that would normally be garbage collected.

My statement was merely to be mindful of this, and place a limit on the number of cache entries that can be stored. Most cache libraries that have a cache of multiple results have the ability to limit the size of the cache.

Hope that provides some clarity, but if you have further questions let me know!

One clap, two clap, three clap, forty?

By clapping more or less, you can signal to us which stories really stand out.