Why not use for...in, for...of, for(airbnb linter)?

Question

JavaScript

Found only this: https://github.com/airbnb/javascript#iterators--nope
Nevertheless, I would like to get a more detailed answer.

Answer 1

Because someone has decided so and his voice has a strong weight. You can always disable this rule.
This is due to the fact that in some browsers everything is bad with iterators, and for..in iterates the properties of the prototype in addition, which is somehow clearly explained in the documentation, and it is impossible to rely on hasOwnProperty in some cases (it is not explained why), probably because it can be redefined for an object, but it can also be redefined for Object, and then everything is bad. Or insufficient browser support.
Summarizing, iterate over the properties of an object, there are arrays for iteration. And properties on that and properties that to them to address directly.

Answer 2

I use for..of on an array only when I need to break the loop ahead of schedule through break. In all other cases - array methods. It just reads faster.
Although I should note that in the case of asynchronous actions, the implementation through reduce is perceived more difficult than await in the for loop, and here I consider it acceptable to violate the requirements of the linter.

Answer 3

Because a callback method from an array prototype is easier to test. For me personally, this is not a convincing argument to abandon procedural searches completely.