The Inconsistent World of JavaScript Array Methods
Description
A two-panel meme from the movie 'The Babadook' depicting a stressed mother driving a car and yelling at her screaming child in the back seat. In the top panel, the mother is labeled 'Any other JS array function' and is yelling, 'Why cant you just be normal?'. In the bottom panel, the screaming child is labeled 'pop(), splice(), shift()'. Below the child, a caption in italics reads '*doesn\'t return new array*'. The meme humorously highlights a common frustration for JavaScript developers: the inconsistency in Array methods. While modern methods like 'map()' and 'filter()' follow functional programming principles by returning a new array without altering the original, older methods like 'pop()', 'splice()', and 'shift()' mutate the original array in place. This can lead to unexpected side effects and is a frequent source of bugs for developers who expect immutable behavior
Comments
7Comment deleted
There are two types of JS array methods: those that politely return a new array, and those that barge into your original array, rearrange the furniture, and leave with an element without asking. We call the second type 'legacy features'
pop() and shift() are the old sysadmins of the JS stdlib - while every other array method opens a PR for an immutable copy, they SSH into prod, delete the row live, and hand you the corpse as the return value
After 15 years of explaining why splice() returns the removed elements instead of the modified array, I've started telling juniors it's a feature that teaches them about defensive copying and the importance of reading MDN documentation before their first production incident
The eternal JavaScript paradox: we've collectively agreed that immutability is the path to enlightenment, yet the language keeps these mutating methods around like that one legacy service everyone's afraid to deprecate. Senior devs know the real horror isn't that pop() mutates - it's explaining to a junior why their React component re-renders are broken because they used splice() instead of filter(). At least we can take comfort knowing that somewhere, a TC39 committee member wakes up in a cold sweat remembering they can't break backward compatibility for the 0.01% of production code still relying on shift() returning undefined on empty arrays
JavaScript array API: 90% 'least astonishment,' 10% pop/shift - where your reducer learns incident response
JavaScript arrays: map/filter look functional; pop()/shift() quietly break referential transparency - mutate your cache and hand you a single element as a receipt
pop, splice, shift: the array methods TC39 designed to keep perf hawks happy while purity zealots rage-quit to immutable.js