chapter four
4 Primitives, Coercion, and Equality
This chapter covers
- Distinguishing between JavaScript’s two representations of nothing: undefined and null
- Understanding why some JavaScript values are considered falsy
- Using symbols to provide guaranteed-unique property keys that prevent naming collisions
- Recognizing where type coercion happens automatically in arithmetic, comparisons, and logical operations
- Choosing between loose equality with its multiple conversions and strict equality that never coerces
- Preventing performance degradation from repeated type coercion in loops and sort functions
- Exploring how V8 optimizes primitives through pointer tagging for zero-allocation storage
Here's a fun bug: a payment system starts double-charging customers because someone wrote if (!transactionId) to decide whether a charge had already been recorded, and the earliest rows in the legacy table were numbered from zero. Zero is falsy, so the check reads "already charged" as "never charged" and runs the charge a second time.
These types of bugs happen all the time. Not because developers are careless, but because JavaScript’s type system is… well, let’s say “quirky”. The same flexibility that lets you prototype quickly with no type declarations, automatic conversions, and forgiving comparisons, also sets traps that will not be noticeable until production.
Let’s consider a simple example that contains three different bugs: