TEA and SPA: A Retrospective
summary
A retrospective on using Elm Architecture for a large proxy web app: claims that it yields fast prototyping but forces a single global state, making encapsulated component state and lazy route code‑splitting hard; reports cursor/DOM glitches from the virtual DOM and that async fetches pollute the Msg union; experiments with Purescript Concur (monadic render sequences) and Halogen for local state and child queries; notes third‑party React integration breaks event threading and finds no mature, type‑safe lazy module loading solution yet.
AI-written summary · about
chapters (4)
related talks
41mHow to Elm-ify Your ML
46m"Melange: The Next Frontier in Type-Safe Web Development"
32m"Making Elm Talk to Your Personal Supercomputer"
39mIntroducing Elixir: Your entire web stack
47mWhirlwind Tour of the Scala Functional Programming Ecosystem
27mEffectful
04mLightning Talks – Przemyslaw Krowinski
06h 28mDay 5