Elm ports and Task scheduling under concurrent messages: controlling UI update latency
Goal An Elm 0.19 application receives messages from several ports and HTTP tasks at roughly the same time. The goal is to keep UI updates responsive when these asynchronous sources emit in bursts, rather than having renders queue up behind a backlog of queued messages. Constraints and uncertainty Elm's runtime is single-threaded and schedules updates on the