WERY GOOD!!!

nice one!

Interesting

I understand that, but indexing the string values would't be a string values aswell? I mean you need numbers to use the operands in this function, or at least I though that.

I'm trying to understand this, so inside the .map function you can declare a variable (in this case "game", but it could be called anything right?) that refers to one element of the array?

Overriding the prototype is definitely not a good practice.

But other than that, this code is simple and that is a good thing.

Sure, it won't be optimal for running anagramm checks for millions of items, but that was not a requirement. Usually if something has to handle big data you know either because it is obvious from the context, or you are told that.

In this case premature optimization would only made the code more complex and thus harder to read and understand. And that can be bad.

The speed of sort is irrelevant for an array of a couple of items and only a handful of invocations. Readability and maintainability is way more important for such cases.

I literally did the same, just because I could. But this is bad. First it's goes N 3 times also sort! and ther are rumors for messing with prototype is no good.

Thanks for this clever solution

sorting a word on every iteration consume extra cpu, rather you can sort word once and use it in filter

sort is very slow. Definitely not a best practice

Nice