I know right. I’m glad DSLs have fallen out of fashion. Just use the platform.

Same, I basically assumed the community around it had died out. But i guess the sole maintainer/creator is still around.

I never used elm except for doing a tutorial, but lately I've built a full stack gleam app (using coding agents for the most part, with a lot of control in the beginning on the structure of the code) and have found that process works quite well

wow careful, this turkey still has some kick left in it!

The project was dead. The previous release was 7 years ago, where it stopped because the creator (same as author of this announcement) stopped maintaining it and since the community hasn't progress beyond a BDFL-model that's where it died.

So it was dead, it just now has been resurrected (and AFAIK with a whithered community in the meantime).

The point is the same as in pre-LLM.

Stronger foundation (as to mean better tested), less accidental complexity of reinventing everything, transferability of knowledge, easier onboarding and review of changes.

Your argument is a mirror of the snark claim "why don't LLMs write in assembly" for those not looking at the output at all.

I haven't tried it, but Elm might be a really good fit for LLMs, because it forbids taking shortcuts.

Professional diligence, perhaps? A desire to not be blindly led into the kind of narrow, often first-party stack which is so often proposed by Claude Code?

With all due respect, not everyone is afflicted with the lack of care sufficient to allow them to launch vibe coded apps as low quality as https://podnami.com. Considered technology choices are one such aspect of the practice of caring about what you're building.

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