Elm in Production: Surprises & Pain Points 

for some reason, this article from 2004 feels current: www.paulgraham.com/pypar.html

I worked with Elm in a company over 3/4 of a year and I can say this: while runtime errors can be completely omitted, your codebase WILL become much more verbose vs the same functionality implemented in pure JavaScript. A good IDE can help you to work much faster with shortcuts and Elm-plugin tho! Also you need to have a good understanding of static functional domain modeling with Elm's type system because, while providing a lot good stuff, it has its restrictions (e.g. no type classes) which make modeling complex business logic very verbose and tedious (e.g. you if you have a union type with a couple of members which are processed by algorithms A, B and C and some members which should be processed with A, B, D, E. So similar behavior sometimes but completely different other times). This actually _increases_ the amount of work instead of reducing it because you are in *statically typed land*. But by the time you HAVE a good code base maintenance and extensions with new features become much easier, provided you don't need to refactor high-level types first, which can be a pain in the bottom! Elm imho is a good choice for businesses which have a clear vision of what they want to achieve with their software and have patience and money to build a long-lasting, high-quality code base without runtime errors, which can be easily extended if well-planned/-modeled. It is NOT a good choice if you don't know exactly what you are going after and you want to rapidly prototype and test lots of different stuffs on the market. Other than that, from a developer perspective, Elm is a very nice language and Ecosystem

Always go with 10 high performers if available. So it's not a question.

Thank you, the thread was very helpful

@@KevinNYank I love how you are combining React with Elm in your portfolio. You mentioned that you use React "for features that aren't well suited to Elm". It would be nice if you could share your feelings on this topic.

Kevin Yank Ahh, OK. I thought it was like a console pane. One last thing. What plugins you use to smoothen your elm dev experience.

It's Operator I believe. A $200 font.

I partially understand, I never ever code using vanilla JS (i was very lucky because that plain language, without tools like babel/typescript, is a serious mess) as I started learning web development with Angular 2. I understand that everyone needs a better tool than plain js, really. I'm waiting for the spread of WebAssembly, i think that should fix the js problem probably better than Elm itself. Erlang will be my 1 choice along C (my background is C that's why probably I kinda love typescript). So yes, (web)dev will change a lot in the next few years, especially because web apps will be more and more become just Apps.

Dialyzer!

Kevin Yank thank you for prompt and clear response!