ElectronJS from the Source

on YouTube ↗29m

" summary

Electron warns that upgrades drive security and fixes: Chrome ships a new major every six weeks (≈600 engineers), Electron follows and releases about every 12 weeks, so staying near Chrome stable is the primary mitigation. Binary fuses flip bits at build time to permanently disable features under code signing. For performance, avoid copying large JSON across processes; use message ports with structured clone to forward ArrayBuffer frames directly. Reproduce regressions with Fiddle bisection to pin the exact Electron version. Build Tools, Forge, the Views API and a proposed Electron N-API header are the concrete tooling paths.

AI-written summary · about

" chapters (15)

1. 0:00Intro
2. 1:23What is Electron
3. 4:45Electron in Chrome
4. 5:50Security
5. 8:17Why Electron
6. 10:08Performance
7. 12:25Multiprocess design
8. 13:39IPC
9. 14:22Message Ports
10. 16:58Electron Fiddle
11. 19:00Issue Tracker
12. 19:52Fork Electron
13. 21:01Use Build Tools
14. 22:15Upcoming
15. 26:15Questions

" related talks

• 58mCross-Platform Desktop Apps with ElectronDavid Neal · NDC Minnesota 2018
• 33mElectron: A Tale of Two ProcessesJessica Lord · JSConf AU 2016
• 54mCross-Platform Desktop Apps with ElectronDavid Neal · NDC Sydney 2018
• 23mHow to ElectronBlaine Schmeisser · NodePDX 2016
• 01h 01mElectron - Writing desktop applications using web technologiesCristian Prieto, Mahesh Krishnan · NDC Sydney 2016
• 39mBuilding Desktop Applications with ElectronCatalin Fratila · Jfokus 2018
• 44mApplication Development with Electron: How and WhyDavid Tanzer · Voxxed Days Zürich 2022
• 25mElectron: Desktop Apps with JavaScriptFelix Rieseberg · Node+JS Interactive 2019