JavaScript @ Spotify
summary
Desktop UI moves from C++ to HTML/JavaScript, exposing native functionality through a C++ client core and Chromium Embedded Framework (SEF) web views; the rewrite aims to speed iteration, improve retina and accessibility support, and allow feature teams to ship faster. Engineering choices: sandboxed UIs via iframes to contain leaks and allow killing views to reclaim memory, a shift to a single monorepo with one build pipeline and an internal npm to avoid cross-repo version drift, and a documented golden path to standardize tooling and testing.
AI-written summary · about
chapters (10)
- 0:00Intro
- 1:09Spotify History
- 3:23Web Build
- 13:15Iframes
- 16:09Horizontal changes
- 17:10Continuous integration
- 19:26Single build pipeline
- 20:34Entropy
- 21:26Golden Path
- 23:37Lessons Learned
related talks
40mScalable JavaScript architecture
23mOverflow: a large scale JS to AngularDart rewrite
56mBrowser Invasion: Desktop Apps and the Web
46mAccessibility vs latest Web APIs. Can’t we just get along?
42mElevating the Web Platform with the JavaScript Framework Community
21mBuilding Cross Platform Desktop App using Web Technologies with Electron
23mJavaScript? In *my* native video app's core streaming library?...
50mRefactor of a Hi‑Fi Music Player in JavaScript
