Let's Admit,
There is that one array method (usually .map or .forEach) which is close to our heart â€ïž and that is the one which we try to use for basically all array operations!
All of you are secretly admitting to the above sentence and thinking, "Is it wrong to do that?"đ€. Well, maybe, may not. But there's no harm in learning something new, right?
In this video, we look into a long time underrated child of Array.prototype and look into whether it covers some of our day to day use cases where the poor old map/forEach is forcefully shoved to work!
Hope that helped, cheers!
Top comments (3)
I though this was on the topic of overusing reduce which was brought up by Jake Archibald recently on twitter.
They were arguing that beside summing, reduce should be avoided in favor of
forloops as they were easier to read and faster.Object.fromEntriescan help remove a lot of reduces too when generating objects.If you want a method to rule them all,
reduceis your best bet, but don't.Learn
mapandfilterthey have very clear and distinct roles, now days I favorfor..ofoverforEach.Yes correct. I brought this up to highlight the other sentiment which is: 'use map/forEach all the time', even in cases where reduce could have been your best bet.
This is another awesome video on the same topic:
Yes well, that's jake haha