Clojure 1.13 adds support for checked keys

Clojure’s latest test release just dropped a small-looking change that sparked a very big feelings-fest: developers can now tell the language to blow up immediately when expected information is missing, instead of quietly sliding along with an empty value. In plain English, that means fewer mysterious crashes later — and way more arguments now. The official pitch is simple: catch mistakes where they start, not after they’ve wandered through your app wearing a fake mustache. There are also some under-the-hood speed and cleanup tweaks, but let’s be honest: the real show is the comments.

One camp basically said, “Wait, wasn’t Clojure’s whole vibe to be chill about missing stuff?” One commenter flat-out asked if this felt "counter to clojure philosophy", which is the kind of sentence that instantly summons a philosophy cage match. Another person admitted they actually like the old way, where missing data often turns into nil and the program keeps moving, calling it more pragmatic and less anxiety-inducing. On the other side, supporters were positively gleeful, arguing that real errors should happen at the moment of the mistake, not later as some random crash that sends everyone on a debugging treasure hunt. One fan predicted lovers of the old “nil-punning” style would soon discover “the joys” of immediate failure — which is such a deliciously smug victory lap it almost deserves popcorn. Even the practical crowd got involved: one team had just upgraded to the current version and is already eyeing 1.13, except, plot twist, it’s still an alpha and that makes managers nervous. Classic developer drama: everyone agrees bugs are bad, but not on how loudly the language should yell about them.