As I note in my other comment, this approach is fundamentally unsound in Elm. The view is generated in its own thread synced to the browser's rendering system.

As I note in my other comment, this approach is fundamentally unsound in Elm. The view is generated in its own thread synced to the browser's rendering system. It is entirely possible for the model to have changed without the view having been updated yet to match. If your model changes under your feet while you use this approach, it result in you silently overwriting that change with the old data.