The problem with reduce is that there are two things happening in parallel. What happens to the accumulator and the function operating on the list. This situation always makes reasoning harder, at least until you've practised a bit.
I guess you can say a for loop has same issue with the iterator and the operations carried out but they are sort of separate things.
The reduce example in the article added a third piece of action, the choice between valid and invalid. To me that is too many moving parts for a functional approach and the latter example using two filters is better.
Yes it is slower with the two list iterations but if you need speed then use a for loop.
Trouble maker and Problem solver ⚙️🔧
Loves simplicity, hates bullshit 💩.
Productivity obsessed, avid learner 🖥🚀
Sport and outdoor freak 🧗⛰
Metalhead 🎸🤘 Father of 2 👨👩👦👦
Opinions are my own
The problem with reduce is that there are two things happening in parallel. What happens to the accumulator and the function operating on the list. This situation always makes reasoning harder, at least until you've practised a bit.
I guess you can say a for loop has same issue with the iterator and the operations carried out but they are sort of separate things.
The reduce example in the article added a third piece of action, the choice between valid and invalid. To me that is too many moving parts for a functional approach and the latter example using two filters is better.
Yes it is slower with the two list iterations but if you need speed then use a for loop.
I really appreciate how you articulated your thoughts. This is how I see it too. Thanks