- 1 Platform Games
- 2 Mozilla Games Technology Roadmap
- 2.1 Roadmap
- 2.1.1 Allow developers to better exploit hardware parallelism
- 2.1.2 Improve cold load time of large compiled codebases.
- 2.1.3 Improve browser storage capabilities.
- 2.1.4 Improve browser graphics capabilities.
- 2.1.5 Allow developers to better avoid 32-bit browser Out-of-Memory conditions.
- 2.1.6 Continue investment in performance across the platform.
- 2.1.7 Continue investment in Emscripten.
- 2.1.8 Continue investment in Firefox developer tooling to better support game developers.
- 2.1.9 Continue implementation of Service Workers to support offline.
- 2.2 Under Consideration
- 2.3 Related Projects
- 2.4 Tracking
- 2.5 Communication
- 2.6 People
- 2.7 References
- 2.1 Roadmap
The platform games initiative is made up of a core team whose works is primarily focused on making the Gecko platform, Firefox Desktop, Firefox OS, and Firefox for Android the best it can possibly be at running games. The core team is ready to help coordinate with other groups in the community who are working on features or optimization that are important to game developers and provide assistance when needed. Platform development continues to focus on games and we hope you are as excited as we are to make HTML5 rock on the web!
Mozilla Games Technology Roadmap
There are two levels to this document. The first is the Roadmap section which contains areas that are currently in development and we have a reasonable level of confidence we can address in the next year. For the topics that are listed in the Under Consideration section, we are actively investigating the best way to address them.
Allow developers to better exploit hardware parallelism
Developers are struggling to get multi-threaded games running efficiently on the Web:
- Standardize, implement and ship SharedArrayBuffer 1,2
- Add pthreads support to Emscripten 1,2
- Expose performance-sensitive Web APIs to Web Workers: WebGL, WebSockets, IndexedDB, WebAudio, WebRTC, WebVR
- Share compiled code (asm.js and WebAssembly) between workers 1
- Developers want to take advantage of SIMD hardware to optimize their code:
Improve cold load time of large compiled codebases.
Developers want to see reduced download, compilation and startup time for multi-million line compiled codebases.
- WebAssembly will provide significant download size reductions (even before native support, through the polyfill) 1.
- Add a fast WebAssembly/asm.js compiler that allows an app to start quickly while a fully-optimizing compilation proceeds in a background thread 1.
- Off-main-thread, streaming parsing/compilation 1.
- Developers want to avoid depending on HTTP Content-Encoding:gzip for generic compression.
- Add Emscripten support to perform decompression in asm.js / WebAssembly while downloading (allowing more aggressive algorithms than gzip).
Improve browser storage capabilities.
- Developers seeking to avoid the permission prompt associated with persistent storage hit limitations of temporary storage as currently implemented in browsers.
- Improve temporary quota limits to take into account factors like frecency.
- Provide more information on quota usage and allowance 1.
- Propose, standardize and implement finer-granularity units of evictable storage 1.
- Allow cross-origin storage usage 1.
- Developers that need persistent storage guarantees hit limitations of persistent storage as currently implemented in browsers.
Improve browser graphics capabilities.
- Ship WebGL2 1.
- Standardize and implement streaming WebGL canvas via WebRTC 1,2.
- Run WebGL on discrete hardware for systems with integrated+discrete (e.g. nVidia Optimus).
Allow developers to better avoid 32-bit browser Out-of-Memory conditions.
- Ship 64-bit Firefox on 64-bit Windows.
- Avoid Emscripten in-memory Virtual File System for asset storage by leveraging pthreads and FileReaderSync to provide synchronous file I/O in workers.
Continue investment in performance across the platform.
- Significantly optimize WebAudio performance 1.
- Reduce WebGL shader compile times 1,2.
- Reduce latency and jitter in the browser’s rendering pipeline 1,2,3,4.
- Continue investments in the performance of JS, DOM, WebGL, WebRTC, codec, layout, rendering, compositing, animation, etc.
Continue investment in Emscripten.
- Add support for pthreads, SIMD, and WebAssembly, as mentioned above.
- Further improve compilation speed.
Continue investment in Firefox developer tooling to better support game developers.
- Improve Web Worker support 1.
- Allow developers to break on various asm.js/WebAssembly error conditions 1.
Continue implementation of Service Workers to support offline.
- Ship Service Workers and dependent features 1.
- Developers are having trouble identifying how many Web Workers they should create to distribute their workload. Benchmarking methods often prove unreliable.
- Developers are hitting the 20-per-origin limit on web workers in Firefox and are requesting a much higher limit.
- Leverage multi-process browser architecture to guarantee a fresh address space for games with large contiguous heaps allocated early in process startup.
- Investigate Out-of-Memory error reporting mechanism to send safe/sanitized triage information back to Web app developers.
- Collaborate on new standards to improve IME capabilities ,2.
- Add hardware cursor API 1.
- Improve Gamepad API 1.
- Add Pointer Clipping extension to Pointer Lock API 1.
- Add Emscripten tooling for memory use/leak debugging.
- Standardize (as part of WebAssembly or more generally) a more scalable form of source maps suitable for large compiled codes.
- Game Focused Benchmarking
- WebAudio Conformance Tests
- IndexedDB File System (posix-like API)
- WebAudio API Rollout Status
- JSIL Porting Tool
- BananaBread Mobile
- BananaBread Multi-player (using WebRTC)
- Awaiting Triage [games:p? or blocks gecko-games]
- No Priority [games]
- P1 [games:p1]
- P2 [games:p2]
- P3 [games:p3]
- Bugs Landed in Mozilla 20
- Bugs Landed in Mozilla 21
- Bugs Landed in Mozilla 22
- Bugs Landed in Mozilla 23
- Bugs Landed in Mozilla 24
|Project Team Meeting|| Wednesdays at 10:00 AM (PST)/1:00 PM (EST) for 60 mins
Games Platform & Research
- Vladimir Vukicevic - <firstname.lastname@example.org>
- Martin Best - <email@example.com>
- Alan Kligman - <firstname.lastname@example.org>
- Alon Zakai - <email@example.com>
- Jeffrey Gilbert - <firstname.lastname@example.org>
- Jukka Jylänki - <email@example.com>
- Luke Wagner" <firstname.lastname@example.org>
- Marco Mucci - <email@example.com>
- Milan Sreckovic - <firstname.lastname@example.org>
- Naveed Ihsanullah - <email@example.com>
- Maire Reavy - <firstname.lastname@example.org>
- Paul Adenot - <email@example.com>
- Ted Mielczarek - <firstname.lastname@example.org>
- Kannan Vijayan - <email@example.com>
- Peter Chang - <firstname.lastname@example.org>
- Christopher Mills - <email@example.com>
- Eric Shepherd - <firstname.lastname@example.org>
Games Partner Support
- Bill Walker - <email@example.com>
- Harald Kirschner - <firstname.lastname@example.org>
- Louis Stowasser - <email@example.com>
- Nick Desaulniers - <firstname.lastname@example.org>
Games Public Relationship Team
- Paul Jarratt - <email@example.com>
- Anthony Hughes - <firstname.lastname@example.org>
- Marc Schifer - <email@example.com>
To Be Kept Informed
- Chloe Varelidi - <firstname.lastname@example.org>
- Dave Herman - <email@example.com>
- Sean Stangl - <firstname.lastname@example.org>
- Jeff Muizelaar - <email@example.com>
- Benoit Jacob - <firstname.lastname@example.org>