The ES spec doesn't require it, but every implementation does insertion order (a... | Hacker News

Hacker Newsnew | past | comments | ask | show | jobs | submit

		gsnedders on July 30, 2018 \| parent \| context \| favorite \| on: Why the New V8 Is So Damn Fast The ES spec doesn't require it, but every implementation does insertion order (and insertion order was a deliberate decision by Brendan in the original implementation, IIRC), and the web very much relies on it. The "new" generation of JS VMs (V8, Chakra, Carakan) all dropped insertion order for array index properties (that is properties whose name is a uint32), but kept it for everything else; that broke about as much as browsers are willing to break, and breaking the general case would be far, far worse.

drb91 on July 31, 2018 [–]

Building a browser sometimes feels like building a language where the only guarantee is the worst features will be used and maintained.

I mean this not as a slight on the ecmascript creators/maintainers but rather as an observation of how difficult the problem is.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact