How to keep your server alive AND teach JS to kids
summary
A production server runs Chromium headless controlled by Headless Chrome and Puppeteer to execute untrusted student pages inside an automatic marker sandbox that enforces CPU and network limits, strips external requests, handles prompts/alerts, times out infinite loops, prevents HTML-injection in feedback, and takes deterministic screenshots. Problem authors write high-level tests that check outcomes not style, emit smart feedback hints, and the system scales to grade‑school submissions while keeping the marker alive.
AI-written summary · about
chapters (8)
- 0:00Intro
- 0:30Why teach JS to kids
- 1:45How we mark our JS
- 5:40Hallow name
- 7:45Modals
- 10:25Meme Maker
- 11:45Feedback
- 13:55Quiz
related talks
35mServer-Side Browsers: Exploring the Web’s Hidden Attack Surface
40mHostile JavaScript: Attacking and Defending the Browser
27mRun your JS everywhere, with Jellyfish
01h 04mJavaScript's Most Wanted
26mTeaching JavaScript to the uninterested
59mThe Final Frontier: Security APIs in Modern Browsers
15mFrancis Bouvier
15mJavaScript and Interactive Installations