Crystal 1.22.0 is an infrastructure release, the kind that doesn't generate headlines but determines whether a language survives its second decade. The marquee change is universal native event loop support: epoll on Solaris, kqueue on all BSD targets, with libevent demoted to opt-in fallback and slated for deprecation. This removes a C dependency that had been a recurring source of build friction and portability bugs since Crystal's early days. The promotion of aarch64-linux (both GNU and musl) from Tier 2 to Tier 1 formalizes what was already functionally true since version 1.19 shipped official ARM builds. This matters because ARM server adoption continues to accelerate — AWS Graviton, Ampere Altra, Apple Silicon CI runners — and Tier 1 status means bugs on these targets now block releases rather than getting triaged as secondary. A revamped DWARF parser addresses a real pain point: backtrace performance. The new implementation scans sections on demand, builds an index table once, and caches decoded lines in an LRU cache. For long-running server processes that hit exceptions, this is a concrete improvement in debuggability without runtime cost. The HTTP stack received extensive hardening: rejection of unrecognized Transfer-Encoding headers, invalid Content-Encoding, and invalid trailers. These are the kinds of fixes that separate a language's stdlib from a toy implementation. Crystal's HTTP server is used in production by its primary sponsor 84codes (makers of LavinMQ and CloudAMQP), so these fixes likely reflect real-world attack surfaces. Smaller but notable: typed constants arrive (BAR : Int32 = 1), STDOUT now emulates SIGPIPE behavior by default (exiting on broken pipe rather than raising), Process.fork is finally removed after years of deprecation, and first-ever builds for aarch64-windows-msvc ship. A forward compatibility policy (RFC 30) now guarantees Crystal 1.22 can be built by any compiler back to 1.14. The release was produced by 33 contributors, with the bulk of heavy lifting done by two core maintainers: @straight-shoota and @ysbaddaden. The project remains primarily funded by 84codes, with additional support through OpenCollective. This funding concentration is both Crystal's lifeline and its structural vulnerability — a single sponsor sustaining a language used by a community that mostly doesn't pay. Kernel TLS support in OpenSSL bindings was enabled by default in 1.22.0 but reverted in the immediate 1.22.1 patch release. This kind of rapid revert is healthy — it signals a project willing to ship aggressively and correct quickly rather than gatekeeping features indefinitely.
