~/talk

10 Things I Learned from Reading the Chrome OS Source Code

TalkinFrenchat DevFest Paris 2015 · on Friday, 2015-01-30· [open-source]
links:none on file
slides:none on file

Describes findings from reading the Chrome OS source: release cadence details (Stable every 6 weeks, Beta every 3 weeks, Dev weekly, Canary daily) and how developer mode on a Pixel can load alternate OS builds and enable a canary flag. Shows hardware/firmware tricks (Pixel lightbar Konami easter egg and injecting shell-command sequences into the firmware UI), measures extension rollout interval (~325 minutes), and demonstrates using chrome://flags and chrome://inspect to view connected Android devices, service workers, camera app JavaScript (with test hooks) and DHCP hotspot options in the source.

AI-written summary · about

  1. 0:00Introduction
  2. 0:22Chrome update channels
  3. 3:14Developer mode
  4. 4:49Light bar on Pixel
  5. 6:12Konami code
  6. 12:13Extension update delay
  7. 15:45CR-48 motherboard
  8. 17:17Chromebook code names
  9. 19:42Chrome OS evolution
  10. 20:45Experimental features
  11. 23:07Inspect system elements
  12. 25:55List and inspect extensions
  13. 28:45Preinstalled extensions
  14. 29:08Chrome comic v37
  15. 31:06Chrome OS update
  16. 33:10Verify features in code
  17. 34:13Camera app
~/search
type to search 6,249 conferences, 138,987 speakers and 185,172 talks
~/help
cmdctrl k
search every conference, speaker and series
/
focus the filter search
h
home
c
conferences
s
speakers
e
series
t
light / dark — the status bar button does the same
?
this help
esc
close this, then clear every filter — or just the search, while you are typing in it

Ignored while you are typing. Pages without a filter rail have no search to focus.