[thiht]

> Elm already was the gold standard when it comes to helpful error messages

I read this all the time about Elm, but did you actually try Elm for a real world project?

I did, and Elm error messages were one of the most painful point of the compiler: they're beautiful but very often completely unrelated to what's actually going wrong. They actually drove me away from the actual errors more than once.

[shritesh]

> did you actually try Elm for a real world project?

I'm actually writing Elm at work and we have two separate Elm apps in production.

YMMV but Elm with elm-graphql has been the most productive and confident I've ever been writing frontend code.