Electron: A Tale of Two Processes
summary
Electron combines Chromium, Node and native OS APIs into two cooperating processes: a main process that controls app lifecycle and spawns windows and separate renderer processes for each UI. Chromium and Node share a single shared V8; a coordinator thread watches a libuv file descriptor to wake Chromium’s message loop so Node events run without a busy loop. IPC (and the synchronous remote wrapper) moves data between processes; invisible renderers act as heavyweight workers. Electron 1.0 ships (May 2016) and powers over 220 apps using 300k+ npm modules.
AI-written summary · about
chapters (15)
- 0:00Start
- 10:22Devtools
- 10:34Popular Dev Tools Extensions
- 11:33Native Api
- 13:12Recap
- 16:14Renderer Process
- 19:19Hidden Renderer Process
- 20:23The Electron Api
- 21:47Ipc and Ipc Renderer Modules
- 23:16Remote
- 25:02Electron Api Demos App
- 25:57Electron Api
- 30:32Package Json
- 31:19The Electron Quick Start App
- 32:34Resources
related talks
01h 01mElectron - Writing desktop applications using web technologies
39mBuilding Desktop Applications with Electron
58mCross-Platform Desktop Apps with Electron
54mCross-Platform Desktop Apps with Electron
33m"The Age of the JavaScript-Powered Desktop
23mHow to Electron
17mBuild Your Next App with Electron
25mElectron: Desktop Apps with JavaScript
