4 ms·
I've worked on two (2) substantial production Elm applications. 1. Healthcare Fall 2017, I started integrating Elm into an AngularJS application after experim
by absynce 7y ago
I've worked on two (2) substantial production Elm applications.
1. Healthcare
Fall 2017, I started integrating Elm into an AngularJS application after experimenting with it on a couple of side projects. After a successful initial feature, I convinced the team to use it for new features. Another couple of developers helped to create the initial version until late 2018. We started in Elm 0.18 and converted it to 0.19. Now a sole part-time college student maintains and adds new features to it.
2. Transportation management
Since January 2019, I work on an Elm project, once again weaved into an existing AngularJS app, with ~34k lines of Elm code. I inherited it with no interaction from the previous developer. It looks like it was introduced in mid-2017 and is currently on Elm 0.19. Although it is not perfect, not always following best practices, it is much easier to maintain than anything I've worked on in the past. On JS apps, I've torn my hair out trying to figure out what is going on and attempting to add new features.
With Elm, I refactor daringly and rest more easily.
Please let me know if you have any specific questions.
- Scarbutt 7y agoSince January 2019, I work on an Elm project, once again weaved into an existing AngularJS app, with ~34k lines of Elm code. Watching a simple example in the elm website, the codes make judicious use of new lines, would you say those 34k lines would represent 17K in js?
- jxxcarlson 7y agoYes, something like that. Almost everyone who writes Elm code uses elm-format which is very "spacey". So foo = 1 is formatted with foo = on one line and 1 on the next, with some leading space.