3D Physics for DOMies
summary
Claims a full 3D physics engine runs at 60 frames per second driving real DOM elements — no WebGL, no canvas, no CSS3 transform primitives — on a stock iPad running Safari. A custom JavaScript renderer spends ~6 ms per RAF frame on iPad, cores: a 36-file render core and ~10-file physics engine, because third‑party libraries failed mobile, DOM, or architecture tests. The engine enforces three commandments (Dom reflow, event loop, texture caching), demos include gravity wells, group-by vector fields and a Hello Galaxy, and the platform is free for deployed apps.
AI-written summary · about
chapters (21)
- 0:00Introduction
- 5:48RequestAnimationFrame
- 9:10Physics Engine
- 15:30Physics Demo
- 18:42Why Physics
- 23:05The Future of Design
- 30:35Hello Galaxy
- 33:45Lean Startup
- 36:40Mark
- 37:07Code
- 39:10When
- 41:55Android support
- 43:23Study Unity3D
- 44:28Gaming vs Web
- 45:59Render to Canvas
- 48:02Standard Model Support
- 49:31Rappers
- 50:04Firefox
- 50:54WebSockets
- 52:06Libraries
- 53:26Importing
related talks
27mMoving Beyond Animations to User Interactions at 60 FPS in React Native
24mSafari in Safari
45mNatural physics simulations and canvas hackery
46mJavascript's comeback story on Mobile
18mDOM animations, almost native
31mCascading Perspectives with THREE CSS3DRenderer
58mRendering performance from the ground up
59mYou can't do that with JavaScript!