Elm stirs after seven years, and its own fans feel gaslit

Faster builds, hashable types, and a pulse on iselmdead.info

Czaplicki, who has steered Elm largely alone, used the note to preview concrete progress: a compiler that builds faster and a coming set of equatable and hashable types. It reads as the first real movement in years.

The context that makes people cautious is the interop story. The 0.18-to-0.19 transition removed users' ability to write custom native JavaScript, funneling all outside integration through the official Ports mechanism. Certain features stayed reserved to the core team. With essentially one maintainer, the community has spun off several forks.

"Why would a company newly choose it in 2026?"

The sharpest doubt came from someone who had already bet a codebase on it:

But in 2026 I'm not sure why a company would newly choose a language that hasn't otherwise been updated in nearly 7 years.

— a Director of Engineering in Boston who shipped production Elm since 0.18

Another recounted where his company's Elm evaluation fell apart:

The core team restricted the ability for users to do any native JavaScript interop, which broke every Elm app that needed any functionality that wasn't in the core library.

— an engineer whose company evaluated Elm

On what a "1.0" label should require, one voice drew a harder line:

Without localization or accessibility support, it doesn't make sense to call your UI framework production ready with a 1.0 version. I think limiting what third-party contributors can bridge from browser APIs killed Elm's momentum for anything but toy projects.

— a commenter on what 1.0 should mean

And from someone who wants the revival to work, the mood was closer to grief:

I love Elm, and I love the community, but I feel a little gaslit here.

— a longtime Elm fan

The update ships syntax. It does not reopen the native interop whose removal these voices keep naming as the thing that stalled Elm in the first place.