`no-array-reduce` should not apply where it's not easily replaceable (objects, JSX)

Applying the rule on this code would mean either adding an IIFE with a for-of loop inside or splitting the object declaration from the application (which requires assertions or dead code in TypeScript)

I think this would be a similar exception to #1348 (of which this issue might be a slight duplicate)

return {
	huge: 'object',
	with: 'many',
	keys: array.reduce(etc)
};

<Display>
	<Title>{title}</Title>
	<Modal>
		<List>{array.reduce(reducer)}</List>
	</Modal>
</Display>

[chasm]

This is a remarkably stupid rule. Instead of simply teaching programmers to use reduce well, just ban it entirely. Really?

If you can replace it with map, then you are using it wrongly. If you can replace it with filter, then you are using it wrongly. And there is no reason to believe that those who use for-of instead will write any more intelligible code.

This rule is patronizing and rude. These rules should help discern good usage from poor usage, not tell me what I can or cannot use.

[fisker]

I don’t really understand why the argument, I disabled no-array-reduce myself. I also disabled some rules wrote by myself, I wrote them not because it’s right, it’s because someone need it.