Elm and Elmish for Backendish
summary
Back-end teams produce a working internal event-journal web UI in a few days using F# compiled to JS, Azure Table/Blob storage and an Azure Function front end. Code totals ~200 lines, model ~100 lines, and the app supports fast searches, selecting events and viewing payloads; live reload and type-safe interop eliminate most custom JavaScript. Uses Fable, the Elmish (Model-View-Update) pattern and Fulma/Bulma for quick styling; the prototype works but needs some extra CSS tweaks for full responsive polish.
AI-written summary · about
chapters (31)
- 0:00Introduction
- 1:24Im a backend developer
- 2:36Motivation
- 2:58Why Elmish
- 4:05Views
- 4:29Postmortems
- 5:44Visualization
- 6:10Upload Status
- 6:47Visualizing Quality
- 8:35Lancaster Gate
- 9:16Statistics
- 9:32Dashboard
- 11:23Commandline Tools
- 12:04Writing a custom website
- 13:49Functional languages
- 14:44FB Freaks
- 15:24What is Elm
- 16:30Model View Update
- 17:20Elm Architecture
- 18:51Elmish
- 19:22FSharp
- 22:13Elm
- 22:37Should I introduce Elm
- 22:58World turning point
- 24:34Event Journal Web
- 25:08Blobstore
- 26:37Webpage
- 27:25Plan
- 28:45Demo
- 37:41CSS
- 40:51Testing
related talks
47mElm or how I learned to love front end development
41mWriting Reliable Web Apps With Elm
53mAdventures in Elm: Events, Reproducibility, and Kindness
19mElm at large (companies)
51mElm-Friendly Functional Programming For The Web
01h 28mFunctional Programming for the Web with Elm
26mDeveloping with Elm in a large application
53mElm in production