it’s important to note

Following this line of thought

despite

each group capture

for which there is a technical reason:

overhead

implicitly casting

randomly

an all-encompassing benchmarks

be vastly faster

defeats

simply

measure

the average number of times

threshold

repeatedly

actual

a grain of salt

interpreting

robust

Perfectly

peek

attempts

despite

under the hood

hood

optimize

claim

extravaganza

benchmarks

There must be some nuance

reductive

it times out

a huge amount of data

experience

confirm

grinding

gains

noticeable

claimed

Disclaimer

Nevertheless

clunkier

associated

dedicated APIs

expense

a clean separation

avoid memory leak

magnitude

benchmarks

actually

precedence

ascending order

fully respected

infamously

insertion order

overhead

an extra step

introduces

reveals

through

suffers

construct

complexity

regardless

all at once

reveal

are interested in

constitutes

enumerable

nuances

performed

intuitively

adequate

Sub-optimal ergonomics

cumbersome

invoking

defensive programming

mechanism

resolution

a reliability hazard

Name collisions

Fortunately

On top of that

resolution mechanism

a ripple effect

as opposed to

indeed

conflated

explicitly defined

invoke

automatically

upon creation

no longer

Unwanted

security hazards

confusion

cause

via

implicitly

obvious

downside

falls short of

consumes

indeed

insertion

strings of small integers

unless

at author time

a variable number

dictionaries

frequent

one-time use in general

delimited

except

Almost everything

a pretty broad term

performance characteristics

benchmarks

break down

remains underused

clumsy

somewhat

a more capable

aspects

a new addition

handy

subreddit

truth

declarative

attempts

grasping for attention

omitted

sentiment

headline

criticism

platform

sentiment

fallback bundles

legacy code

penalizes

Mindlessly transpiling

Mindlessly

legacy

opinionated

appeared

evolved with the language

deal with

hesitate

potentially

I guess the takeaway from this is

index-based

destructuring

protocol

actually

garbage collection

associating

legitimate

mention

plain objects

advisable

serialise

disadvantage

unmentioned

pointer access

exploring this area

have a uniform interface

a valid use case

insertion order

maintained

specified

absolutely standard

totally

is definitely more handy than

make a shout-out

optional second argument

every single time

converting

optimized

concerned

performance

certain

as well

frequently

there are not iteration utils

threshold

slowly add up

overall

a soft "rebuttal"

comment

suppress

assertion

scenario

Definitely

structure

awkwardness

relatively logical

incorporate

I think you made a fair point

nested-array