Building Single Page Web Applications with Purescript and Erlang
summary
A working visual IDE for PLCs gets built and runs in the browser using Purescript, Halogen, websockets and BERT for transport, with PLC code compiling to compiles to beam files on-device and Cowboy pushing state so the UI shows per-variable histories and debugger traces. Porting moves from Elm to PureScript, trading Elm simplicity for PureScript’s advanced types and components; BERT claims roughly 30 frames per second interactivity and an order‑of‑magnitude speed advantage over JSON.
AI-written summary · about
chapters (25)
- 0:00Intro
- 0:21Our Project
- 2:14Deployment
- 2:47Requirements
- 3:11Frontend Tech Choice
- 3:39They're breeding like rabbits!
- 4:57Our Second Choice
- 6:05Purescript Pros vs JS
- 6:59Pursuit
- 7:24Milestones
- 7:49Type holes and Search
- 9:34Why Purescript after Elm?
- 11:04Philosophy Differences
- 11:43Reflection on Elm - Purescript - Haskell
- 13:35Frameworks Overview
- 15:23Pux Structure
- 16:28Thermite
- 17:49Halogen Structure
- 18:40Porting choices
- 19:57Backend Communication
- 20:56Getting our bearings
- 22:24Halogen Component
- 24:14Purescript Conclusion
- 25:03Higher Abstractions in Erlang
- 25:25Steps to get started with Purescript
related talks
46mBuilding a Graphical IDE in Elm/Purescript (...)
22mBuilding WebApps Like It's 1972 🧙♂️by Leandro Ostera
47mElm or how I learned to love front end development
01h 28mFunctional Programming for the Web with Elm
41mWriting Reliable Web Apps With Elm
39mWeb Apps in Clojure and ClojureScript with Pedestal
54mBeyond JavaScript Frameworks: Writing Reliable Web Apps With Elm
39mDeveloper Happiness on the Front End with Elm