[appsappsapps]

Every single comment here is focused on just one aspect of this article: speed. Far more interesting points the article covers are around _how_ Elm optimizes and _how_ developers optimize Elm code. From the conclusion:

- Optimizing Elm only touches view code, unlike everyone else.

- Optimizing Elm cannot introduce sneaky bugs, unlike everyone else.

- These results should generalize to apps of any size.

Also interesting is how Elm's immutability allows it to use requestAnimationFrame by default, which plain vanilla JS libs can't use by default.

[Mickydtron]

A related anecdote: One of the major reasons I decided to give elm a try was when Richard Feldman was giving a talk about writing Dream Writer in elm, and he got to a point where the performance was noticeably slowing down. He started trying to make it better by 'sprinkling a few `lazy`s through the view code', and then stopped because that had magically made everything super fast again.

[Zimm_i48]

This is because people comment without actually reading the article :/