There's a lot to love about Elm, and I've written quite a bit of production code with it starting around 0.18.0. 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.

▲

auslegung 4 hours ago | parent [-]

Stability. It works. Frequent breaking changes to core functionality of your tech stack is not a feature, it’s a bug.

▲

Munksgaard 4 hours ago | parent | next [-]

Does it though? They are many longstanding bugs reported in their compiler repository, and this release doesn't seem to address any of them.

▲

auslegung 3 hours ago | parent [-]

Longstanding issues that prevent usage? Not for me and the projects I’ve been apart of. No doubt there are plenty of reported issues, and no doubt they truly negatively impact some users, but I would still much rather choose the usability and stability of Elm 0.19.1-2 than anything in the typescript ecosystem today

	▲	sheept an hour ago \| parent [-]
		When I worked on an Elm app in 2020, my users reported compatibility issues with various browser extensions (e.g. Grammarly, 1Password). I personally would prioritize making my apps usable for my users over making the DX usable for myself, so I stopped using Elm for future projects.

▲

nh23423fefe 4 hours ago | parent | prev [-]

Weird not to mention Elm's massive breaking change that killed the project?

	▲	auslegung 3 hours ago \| parent [-]
		How does that bear on my comment?