Bridging the Gap with Gleam & Lustre
summary
Demonstrates that Gleam multi-target compilation plus Lustre server-side components let a single UI component share logic between BEAM and browser with minimal changes, showing Gleam multi-target compilation and Lustre server-side components in action. A small app is migrated live, with the component rendering identically on server and client except for one runtime linkage difference and no data-model rewrite. Shows the built example working after migration and the actual toolchain commands used.
AI-written summary · about
chapters (5)
- 0:00Gleam and Lustre intro
- 4:31Java needs modern alternatives
- 10:05Migrating from Java to Gleam
- 14:32Building Lustre components
- 18:38Closing & Q&A
related talks
41mGleam: Lean BEAM typing machine
21mLessons from Building a game engine from scratch in Gleam
01h 02mYour next favorite programming language: Gleam
51mA Glimmer of Hope: Creating Modern Web Components with Glimmer
38mDemos and Lightning Talks
19mLumen
44mLumen - Bringing the BEAM to WebAssembly and Beyond
26mseL4 and BEAM: A match made in Erlang