Quite often, I’ll be in the middle of working on something while riding the train when I have to get off at my stop. The more focused I am, the more I fear being pulled away from things. I try to break tasks in to smaller pieces to minimize the impact of this forceful ejection, but it destroys my flow.
I don’t have this fear with Elm .
As Adam Waselnuk put it :
As you program in Elm, you follow a delicious breadcrumb trail of extremely readable compiler error messages until the program compiles and everything works.
I’ve not only found this to be true, I’ve found that because those breadcrumbs will still be there later, the error messages from the Elm compiler become a sort of continuation that I can use to pick up right where I left off, even days later. Fixing errors as the compiler presents them to you provides many natural stopping points.
I thought Elm was a pure, functional language, but this is one hell of a side effect.