I'm not sure I understand, if this is a satire piece then I missed it completely.
All the examples provided, are far more readable than the author's own examples. Perhaps, it is because those operations are inspired by Functional Programming concepts, and has commonality across many different languages.
Putting performance aside (for now), these examples shows intent. It tells the 'what' rather than the 'how'. In one glance, I can tell what the first code is supposed to be doing, not so much with the for loop of the second one where I have to inspect and step-through the algorithm (in my head).
In my personal experience as well, for loop implementations need to be accompanied with comprehensive tests as it is easy to make a mistake in them.
Performance matters, but I do believe readability and correctness matters more.
I would have been fine if the focus of the article was simply on performance of conventional, imperative JS code. However, it should be acknowledged that readability and comprehension is way lower.
Not so much of a problem, but rather that for loops carry higher cognitive overload, whereas map or filter is composable and easier to comprehend (e.g. treating it as data pipeline).
So there is definitely a tradeoff, readability vs performance.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I'm not sure I understand, if this is a satire piece then I missed it completely.
All the examples provided, are far more readable than the author's own examples. Perhaps, it is because those operations are inspired by Functional Programming concepts, and has commonality across many different languages.
Putting performance aside (for now), these examples shows intent. It tells the 'what' rather than the 'how'. In one glance, I can tell what the first code is supposed to be doing, not so much with the for loop of the second one where I have to inspect and step-through the algorithm (in my head).
In my personal experience as well, for loop implementations need to be accompanied with comprehensive tests as it is easy to make a mistake in them.
Performance matters, but I do believe readability and correctness matters more.
I would have been fine if the focus of the article was simply on performance of conventional, imperative JS code. However, it should be acknowledged that readability and comprehension is way lower.
The article posts a question "why", and I think there has been quite a few potential answers to that question.
Not sure where you see many issues with loops though, care to elaborate with examples? =)
Missed the reply notification 😬
Not so much of a problem, but rather that for loops carry higher cognitive overload, whereas
maporfilteris composable and easier to comprehend (e.g. treating it as data pipeline).So there is definitely a tradeoff, readability vs performance.