Amazing

this is amazing code, i learn new thing. thanks :)

This is really Great, something new to learn today! Thanks to the person who wrote this! I really like this.

Ah, I really like this, very good!

very nice!

what a time to be alive to watch this code

Very nice code

I'm no expert but I think they're saying it's not good practice because not only is it overcomplicated for a fairly simple task, it also would probably suffer a bit in performance compared to the other solutions. That's just my assumption though and I am not great at evaluating whether or not a solution is good practice.

why not best practice?

man, that one is a piece of code. Bravo mon ami, Bravo!

This one is perfectly readable. It's easy to just glace at the templates and to see what this function is expected to return. 👍

I like this solution because it's not the localizations nightmare, since copies would get translated inidividually and the translators have the context of each copy, instead of translating each bit seperately and sticking it together.
Not all languages are LTR or use the same format as English.

To my understanding, when you create a copy it's a reference to the original variable, not a mutatable copy. So that would be a no.

Unless you're talking about individual array elements which can be mutated.

Clever indeed but not best practise.

Too sophisticated for the need at hand, but creative nonetheless. One notable issue is the function shift, it introduces a needless O(N) time-complexity.