Elm at Pacific Health Dynamics
mordrax.gitbooks.io
Elm at Pacific Health Dynamics
1–10 of 57 posts
Re: Elm at Pacific Health Dynamics
#2Took me a while to realize this wasn't about the Elm email client https://en.wikipedia.org/wiki/Elm_(email_client)
Re: Elm at Pacific Health Dynamics
#3Took me a while to realize this wasn't about the Elm email client https://en.wikipedia.org/wiki/Elm_(email_client)
I'm curious how you interpreted the very first sentence on the page:
> the technical trials and tribulations he faced, the euphoric and … not so euphoric bits of writing a SPA in Elm
What trials and tribulations did you picture that came with writing a single page application in an email client?
Re: Elm at Pacific Health Dynamics
#4I've only used Elm for a hobby project. Given how much I enjoyed the experience of web app programming for once, it's nice to read how well it scales to a large application.
Re: Elm at Pacific Health Dynamics
#5Thanks for warning about compile times.
Re: Elm at Pacific Health Dynamics
#6I never enjoyed frontend programming until I came across Elm. Not only that Elm turned out to be a gateway drug to Haskell. Now I write frontend and mobile apps in Haskell using Functional Reactive programming (FRP).
Re: Elm at Pacific Health Dynamics
#7Took me a while to realize this wasn't about the Elm email client https://en.wikipedia.org/wiki/Elm_(email_client)
I'm curious how you interpreted the very first sentence on the page: > the technical trials and tribulations he faced, the euphoric and … not so euphoric bits of writing a SPA in Elm What trials and tribulations did you picture that came with writing a single page application in an email client?
Honestly, it took digging through multiple pages to figure out what (this) Elm was about. If you come in with a preconceived notion of what something is supposed to be about, and there is nothing which even gives a short blurb on project goals, it can be a little bewildering. Clearly it wasn't about the email client (that was a bit tongue-in-cheek), but I was curious about what the project actually was for, and had to really hunt to find any information.
Re: Elm at Pacific Health Dynamics
#8The lead paragraph is a bit worrying.
> Since July 2017, I’ve been leading the frontend rewrite of their flagship product. The codebase was at 16k LoC when I started. Since then, I’ve rewritten the various subsystems at least once (I'm looking at you generic form component). Now we hover around 45k LoC with most of the common SPA structures stabilizing. We are about a third of the way to completion.
I don't know if it's common for rewrites to triple the amount of code while being only 1/3rd complete, but it certainly doesn't feel like "these are the facts I should lead with."
Edit: I read more of the prologue, and it turns out that the initial 16kloc application was not complete.
Re: Elm at Pacific Health Dynamics
#9Earlier quoted context omitted.
I'm curious how you interpreted the very first sentence on the page: > the technical trials and tribulations he faced, the euphoric and … not so euphoric bits of writing a SPA in Elm What trials and tribulations did you picture that came with writing a single page application in an email client?
Honestly, it took digging through multiple pages to figure out what (this) Elm was about. If you come in with a preconceived notion of what something is supposed to be about, and there is nothing which even gives a short blurb on project goals, it can be a little bewildering. Clearly it wasn't about the email client (that was a bit tongue-in-cheek), but I was curious about what the project actually was for, and had t…
It's interesting how everyone thinks they're the first person to make the joke.
Not much different than going "haha, I thought it was about the Elm tree for a while!"
I'm starting to think it's just a way to signal to others that you know of an email client that last had a stable release 12 years ago that most people haven't heard of. Maybe there should be a way to wear this badge of honor in your profile instead of making the same joke, though.
Re: Elm at Pacific Health Dynamics
#10Thanks for writing this. It's encouraging to read about others' experiences using Elm in production. After a couple small side projects in Elm, I'm finally using it in a few low-risk areas at work.