It might be easier to read when you have pages of code with many different functions.

I was wondering why it was specificed that the array was always odd. I understand that now

Thank @Awesome A.D.. I did not know.

Please don't post solutions in the discourse without the spoiler flag.

Going to go out on a limb thinking it's more efficient to have one method that allows you to combine values any way you like vs the structure of the various operations.

it is what it is

Thanks for explanation ( ͡° ͜ʖ ͡°)s

( ͡° ͜ʖ ͡°)

classic case of Stockholm Syndrome

javascript developers prefer their language to be missing fundamental features and to have vast assortment of really broken basic amenities. and/or they're being held hostage.

The explanations I have seen suggest that for short lists sorting and slicing can be faster but sorted() starts to chug on big lists, so min() max() is better practice when you don't know how big the list is going to be.