The Compute Revolution You’re Ignoring: JavaScript in Science
summary
Claim: modern JavaScript plus stdlib runs real scientific workloads inside the browser, cutting latency and installs. Evidence: three implementations of an image inversion—client/server, Pyodide (numpy + scikit‑image), and native JS with stdlib—run 10 iterations at 21 ms vs 121.7 ms vs >4s; Pyodide also needs Pyodide 2–5s load. Working demos include multilingual translation, semantic image search, background removal, OCR with tesseract.js, and toxicity detection via on‑device models.
AI-written summary · about
chapters (10)
- 0:00JavaScript in science intro
- 2:07Three eras of computing platforms
- 8:15Browser era for science
- 10:06Performance comparison
- 17:42Advantages of web computing
- 19:48Five JS demos
- 25:53Building JS science ecosystem
- 31:35Standard Lib library
- 35:27Future of web science
- 38:43Closing & community
related talks
17mJavaScript and mathematical computing across servers and clients
40mJavaScript ... for Science!
46mHow much performance can you get out of JavaScript?
15mThe future of machine learning using JavaScript
30mNative Speed on the Web: JavaScript and asm.js
39mHow much performance can you get out of Javascript?
25mGetting Over Moore's Law: Parallelization Using JavaScript in the Browser
26mPyPy.js: What? How? Why?
