MozillaWiki

Platform/Games: Difference between revisions

Page Discussion

Platform/Games (view source)

Revision as of 00:50, 10 June 2016

405 bytes removed ,  10 June 2016
Structure cleanup - first pass - MVP
(→‎Tracking: Removed unnecessary bugs)
(Structure cleanup - first pass - MVP)
Line 1: Line 1:
=Platform Games=
=Platform Games=


The platform games initiative is made up of a core team whose works is primarily focused on making the Gecko platform, Firefox Desktop, 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!
The platform games initiative is made up of a core team whose works is primarily focused on making the Gecko platform, Firefox Desktop, 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.
 
==Roadmap==


==Mozilla Games Technology MVP Requirements==
The
===Allow developers to better exploit hardware parallelism===
===Allow developers to better exploit hardware parallelism===
Developers are struggling to get multi-threaded games running efficiently on the Web:<br>
Developers are struggling to get multi-threaded games running efficiently on the Web:<br>
Line 19: Line 16:
**DONE - Add SIMD support to Emscripten [https://github.com/kripken/emscripten/labels/SIMD 1].
**DONE - Add SIMD support to Emscripten [https://github.com/kripken/emscripten/labels/SIMD 1].


=====Tracking=====
<bugzilla>
<bugzilla>
{
{
Line 27: Line 23:
}
}
</bugzilla>
</bugzilla>
===Improve cold load time of large compiled codebases===
===Improve cold load time of large compiled codebases===
Developers want to see reduced download, compilation and startup time for multi-million line compiled codebases.
Developers want to see reduced download, compilation and startup time for multi-million line compiled codebases.
Line 37: Line 32:
**Add Emscripten support to perform decompression in asm.js / WebAssembly while downloading (allowing more aggressive algorithms than gzip).
**Add Emscripten support to perform decompression in asm.js / WebAssembly while downloading (allowing more aggressive algorithms than gzip).


=====Tracking=====
<bugzilla>
<bugzilla>
{
{
     "bug_id":"1188259",
     "f1": "blocked",
    "o1": "anywords",
    "v1": "1188259",
    "resolution": "---",
 
     "include_fields":"id, summary, status, assigned_to, target_milestone",
     "include_fields":"id, summary, status, assigned_to, target_milestone",
     "order": "bug_status"
     "order": "bug_status"
}
}
</bugzilla>
</bugzilla>
 
===Improve browser storage capabilities===
===Improve browser storage capabilities.===
*Developers seeking to avoid the [https://storage.spec.whatwg.org/#dom-storagemanager-requestpersistent permission prompt] associated with persistent storage hit limitations of temporary storage as currently implemented in browsers.
*Developers seeking to avoid the [https://storage.spec.whatwg.org/#dom-storagemanager-requestpersistent 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 [https://en.wikipedia.org/wiki/Frecency frecency].
*Improve temporary quota limits to take into account factors like [https://en.wikipedia.org/wiki/Frecency frecency].
Line 57: Line 54:
**Improve storage management/eviction UI for browser users.
**Improve storage management/eviction UI for browser users.


=====Tracking=====
<bugzilla>
<bugzilla>
{
{
Line 65: Line 61:
}
}
</bugzilla>
</bugzilla>
===Improve browser graphics capabilities===
===Improve browser graphics capabilities===
*Ship WebGL2 [https://bugzilla.mozilla.org/show_bug.cgi?id=889977 1].
*Ship WebGL2 [https://bugzilla.mozilla.org/show_bug.cgi?id=889977 1].
Line 71: Line 66:
*Run WebGL on discrete hardware for systems with integrated+discrete (e.g. nVidia Optimus).
*Run WebGL on discrete hardware for systems with integrated+discrete (e.g. nVidia Optimus).


=====Tracking=====
<bugzilla>
<bugzilla>
{
{
     "bug_id":"889977,1161913,1271478,1136734,1169000,1184283,863316",
     "bug_id":"889977,1161913,1271478,1136734,1169000,1184283,863316",
     "include_fields":"id, summary, status, assigned_to, target_milestone",
     "include_fields":"id, summary, status, assigned_to, target_milestone",
     "order": "bug_status"
     "order": "bug_status"
}
}
</bugzilla>
</bugzilla>
===Allow developers to better avoid 32-bit browser Out-of-Memory conditions.===
===Allow developers to better avoid 32-bit browser Out-of-Memory conditions.===
*Ship 64-bit Firefox on 64-bit Windows.
*Ship 64-bit Firefox on 64-bit Windows.
Line 90: Line 84:
*Continue investments in the performance of JS, DOM, WebGL, WebRTC, codec, layout, rendering, compositing, animation, etc.
*Continue investments in the performance of JS, DOM, WebGL, WebRTC, codec, layout, rendering, compositing, animation, etc.


=====Tracking=====
<bugzilla>
<bugzilla>
{
{
Line 98: Line 91:
}
}
</bugzilla>
</bugzilla>
===Continue investment in Emscripten===
===Continue investment in Emscripten===
*Add support for pthreads, SIMD, and WebAssembly, as mentioned above.
*Add support for pthreads, SIMD, and WebAssembly, as mentioned above.
Line 107: Line 99:
*Allow developers to break on various asm.js/WebAssembly error conditions [https://bugzilla.mozilla.org/show_bug.cgi?id=1088655 1].
*Allow developers to break on various asm.js/WebAssembly error conditions [https://bugzilla.mozilla.org/show_bug.cgi?id=1088655 1].


=====Tracking=====
<bugzilla>
<bugzilla>
{
{
Line 115: Line 106:
}
}
</bugzilla>
</bugzilla>
===Continue implementation of Service Workers to support offline===
===Continue implementation of Service Workers to support offline===
*Ship Service Workers and dependent features [https://bugzilla.mozilla.org/show_bug.cgi?id=903441 1].
*Ship Service Workers and dependent features [https://bugzilla.mozilla.org/show_bug.cgi?id=903441 1].
=====Tracking=====
 
<bugzilla>
<bugzilla>
{
{
Line 130: Line 120:
}
}
</bugzilla>
</bugzilla>
== Under Consideration==  
 
== Under Consideration==
*Developers are having trouble identifying how many Web Workers they should create to distribute their workload.  Benchmarking methods often prove unreliable.
*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.
*Developers are hitting the 20-per-origin limit on web workers in Firefox and are requesting a much higher limit.
Retrieved from "https://wiki.allizom.org/Special:MobileDiff/1136641"