Turns are Better than Radians (2022)

The case for turns is deceptively simple: one turn equals 360 degrees, or 2π radians, and suddenly everything clicks. When you write `angle = 0.25` in code, you instantly know that's a quarter-circle—no mental conversion from radians to degrees or vice versa. The article likely points out how radians, while beautiful in calculus, are a historical accident from arc-length definitions that don't map well to human intuition or most programming tasks. What's particularly compelling is how turns align with modular arithmetic. A turn is a complete cycle, so `angle % 1.0` gives you the position on a circle cleanly. In radians, you're stuck with `angle % (2 * Math.PI)` and the constant's irrationality creeping into every comparison. For game development, robotics, or any real-time system, this isn't just cosmetic—it's a reduction in cognitive load and error-prone conversions. The article probably also touches on how radians dominate because of their mathematical pedigree, not because they're practical. In physics and pure math, radians make derivatives of trig functions elegant, but in applied programming, that elegance rarely matters. Meanwhile, turns are dimensionless, scale-free, and directly map to the idea of "how many times around." It's a classic case where the "correct" abstraction for theorists is the wrong tool for practitioners. There's also a cultural angle: we're so used to degrees and radians that turns feel almost childish. But the author makes a strong point that our units should serve us, not the other way around. If we redesigned angle measurement from scratch, turns would likely win. This article is a refreshing nudge to question even our most foundational constants—and maybe adopt a unit that actually makes sense.