Using Linq is adhering to KISS. Yes Linq has performance issues (though often overstated and it does get better with each iteration of .Net) but in 99% of use cases Linq won't be your performance bottleneck and if it is then you can just not use it in those cases.

The advantage of Linq is easier to write/read code. It is far more concise without losing any readability (assuming everyone is passingly familiar with the syntax).

I don't know why you are so enthusiastic about Linq. It sucks (at least for every kata I've seen here thus far).

It is horribly slow, yet people keep using it like it is somehow some godsend. It's allowing people to make horrendous code while they think it's somehow special. More like special-ed...

It's lazy, crappy code...kata after kata. People seem to have forgotten KISS

Good question but terrible description aand broken sample test cases. Please fix them!

Those are two lists with 3 items, the structure is the same.

Not a kata issue, they have the same nested structure, not the same items: sameStructureAs.

Can you please edit the writing part? It is pretty ugly and confusing. It can be done better. :)

As a sugegstion you could preload the houses array so people don't need to copy paste it in the code

this blow my mind

Where does he ask that? He sets up a recursive relationship with a single integer input. Would you consider factorial(x) to be a map/filter/reduce kata?

Thanks for the feedback. They're pretty random now

Thanks! now the js test cases doesn't use assert.deepEqual instead they use assert.closeTo

The issue is not the possible use of map/filter/reduce functions, but the fact that the author is asking to write a for loop mapping/filtering/reducing something.

I understand that you could use map/filter/reduce, but I don't think that is the only, or even easiest way.

It seems a bit pedantic to be marking an issue, just because certain functions/tools could be used to solve it.