When I start a new project meant for production, I need to evaluate whether to use Elm or something else. Elm is good and gives a lot, so I am willing to put up with some workaround and the occasional reimplementation of a smaller JS library. But what are the real dealbreakers? What are the thing…

I have no skin in your game, so take my answers with a grain of salt. [image] xarvh: Large codebases: a breaking change in a library means that the whole app must be upgraded in one go; if the codebase is large enough this might not be possible. Beyond a certain size, the compiler may become sl…

[image] xarvh: Beyond a certain size, the compiler may become slow or very memory hungry. I have been generating code for AWS APIs, and since AWS have a lot of APIs, I ended up with a lot of Elm code. I should really repeat this experiment as it has been a while… I found that the 0.19.1 compi…

[image] xarvh: Lack of asynchronous code loading. Elm static typing does not really allow for coding in extensible ways - not like in OO programming where runtime plugins are commonplace. Javascript certainly allows for this. The ways I think you could do it with Elm, are to have multiple se…

[image] xarvh: Slow bug fixing. I ran into an issue yesterday when trying to publish a package, but it failed to load the docs of the previous build to run elm diff against. The docs are fine, apparently this is a bug introduced in 0.19.1, in rare circumstances it failes to decode its own doc…

I’d second @Philip_Krueger about breaking changes. I’ve done large (thousands of lines of code) refactors is React, Ember, and Elm. Elm was by far the easiest. I personally have yet to find a JS library I couldn’t use with any of my Elm projects. I also know multiple ways to hack around interop wit…

Reasons to use Elm: It’s type system will make you design better code; it’s libraries are well-designed; and it works amazingly well for re-factoring large projects. Reasons not to use Elm in production (you more or less covered them but I want to emphasize their potential effects): It can be com…

On the topic of compile times, Elm should be pretty fast! I tried to gather some numbers on it in this repo . Notable data points include: Lines Build From Scratch Median Incremental Build 136,049 2454ms 638ms 278,803 4059ms 825ms There are some outliers in the data, like this one , whe…

[image] evancz: P.S. I have not heard of object files getting so big that they wouldn’t fit on the heap! Not til @rupert mentioned it here! I believe adding something like +RTS -A512m -RTS will let you increase the heap size as he says though. I should definitely repeat my experiment and repo…

[image] rupert: I have been generating code for AWS APIs, and since AWS have a lot of APIs, I ended up with a lot of Elm code. I Is that this repository ?

@Philipp_Krueger I’ve heard there are some problems with extensions, too, e.g. grammarly. I think that’s also the case for other vdom approaches (e.g. React). This is very interesting, I didn’t know about it. Could you point me to some resources on the topic? @rupert The ways I think you coul…

When should I not use Elm in production?

Learn

Philipp_Krueger August 19, 2020, 7:33am 12

Topic		Replies	Views
Are those downsides still valid today? Learn	12	2838	February 23, 2021
Making the case for Elm at my company. Looking for help! Request Feedback	26	3901	March 13, 2019
What are your favorite things about Elm? Request Feedback	72	6251	April 26, 2021
Elm - What are the risks? Learn	48	3566	February 24, 2021
Two experiences with Elm Show and Tell	26	8509	March 21, 2018

When should I *not* use Elm in production?

Related topics

When should I not use Elm in production?