web-games

原文涵盖的主题

• Web Browser Game Development
• 1. Framework Selection
• Decision Tree
• Comparison (2025)
• 2. WebGPU Adoption
• Browser Support (2025)
• Decision
• 3. Performance Principles

Framework selection and browser-specific principles. -- | Framework | Type | Best For | |-----------|------|----------| | Phaser 4 | 2D | Full game features | | PixiJS 8 | 2D | Rendering, UI | | Three.js | 3D | Visualizations, lightweight | | Babylon.js 7 | 3D | Full engine, XR | -- | Browser | Support | |---------|---------| | Chrome | ✅ Since v113 | | Edge | ✅ Since v113 | | Firefox | ✅ Since v131 | | Safari | ✅ Since 18.0 | | Total | 73% global | New projects: Use WebGPU with WebGL fallback Legacy support: Start with WebGL Feature detection: Check navigator.gpu -- | Constraint | Strategy | |------------|----------| | No local file access | Asset bundling, CDN | | Tab throttling | Pause when hidden | | Mobile data limits | Compress assets | | Audio autoplay | Require user interaction | 1. Asset compression - KTX2, Draco, WebP 2. Lazy loading - Load on demand 3. Object pooling - Avoid GC 4. Draw call batching - Reduce state changes 5. Web Workers - Offload heavy computation -- | Type | Format | |------|--------| | Textures | KTX2 + Basis Universal | | Audio | WebM/Opus (fallback: MP3) | | 3D Models | glTF + Draco/Meshopt | | Phase | Load | |-------|------| | Startup | Core assets,

这里只展示节选，请以完整原文和当前要求为准。