Purely Functional Web Apps
summary
Claims a full pipeline: a Haskell backend that uses haskell-servant to expose a single type-level API, a fetcher that pages through ~1,000 GitLab merge requests into in‑memory storage, a pure business function that computes per-merge stats, and an Elm frontend that pulls JSON every five seconds and renders via Elm virtual DOM. The API type also generates docs and an autogenerated JavaScript client. Code paths and side effects are explicit and compile-checked.
AI-written summary · about
chapters (20)
- 0:00Start
- 1:00MAIN DEV GOALS
- 2:47Application Architecture
- 3:29One slide Haskell tutorial
- 6:24Haskell Servant
- 7:13Gitlab API
- 7:44Merge Request Data Type
- 9:53API Type
- 16:48all MergeRequests function
- 18:05allMergeRequests implementation
- 18:58Side Effects without 10?
- 20:07Business Logic: Stats Calculations
- 21:17fetchRsAndSaveStats function
- 24:01Serving the stats
- 24:42main function
- 26:10Let's do the frontend
- 28:18Elm architecture in types
- 29:37update Function
- 32:45Fame & Glory
- 33:05Time Travel Dehugger
related talks
41mWriting Reliable Web Apps With Elm
51mElm-Friendly Functional Programming For The Web
58mDeveloping Web Applications with Haskell
45mElm and Elmish for Backendish
23mIntegrating Web Apps
01h 28mFunctional Programming for the Web with Elm
43mThe Pure Functional Web
47mElm or how I learned to love front end development