4 ms·
I feel like you could go more into depth to defend your assertion "no memo is not an option." As someone who has spent hours on jsperf back in the day -- my app
by mattwad 5y ago
I feel like you could go more into depth to defend your assertion "no memo is not an option." As someone who has spent hours on jsperf back in the day -- my apps feel blazing fast already. Many devs I know also don't use memo or useCallback at all. It sounds like you're adding an entire layer of extra abstraction "just in case." But then again, maybe your use case makes it warranted.
- eatonphil 5y agoSame, I haven't seen a need for it for performance yet across a few companies and open source apps I've worked on.
- eh9 5y agoEvery single time I’ve needed to use memo the performance gains where obvious.
- sibeliuss 5y agoA: You'll know when you need it. Until that point one is firmly in the realm of premature optimization.
- atom_arranger 5y agoThe post points out that given memoization in many cases avoids serious perf/functional issues not memoizing may be considered premature optimization.