[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Public WebGL] GL_RENDERER string needed for performant apps



+1

I suspect the Google Maps situation is the norm outside of technology demos.  Access to the GL_RENDERER string will certainly be a huge benefit to our WebGL applications.

Kevin


On Mon, Jan 13, 2014 at 6:39 PM, Jennifer Maurer <maurerj@google.com> wrote:
The Google Maps and Chrome teams recently conducted an experiment where the GL_RENDERER string was made available via WebGL for 5% of users, so that the performance implications could be quantified. Using this data we have conclusively determined that access to the GL_RENDERER string is required in order to provide a good user experience in the new Maps product, which uses WebGL as its preferred rendering API.

In response, Google Chrome plans to enable access to the WEBGL_debug_renderer_info extension universally, allowing all WebGL applications to access this information. Ideally, we would like all WebGL implementers to follow suit, in order to provide the best user experience for the new Maps and other complex WebGL applications.

In addition, we are petitioning the WebGL working group to remove the security warnings from this and the WEBGL_debug_shaders extensions, as we believe that exposing this information is not as privacy-sensitive as once feared, and the benefits of making it available to real-world WebGL applications have been clearly demonstrated.

Please send feedback on this plan and the proposal for the WebGL extensions to the mailing list.

For further information, please see http://goo.gl/dxRdGS
~Jennifer



--
www.kotachrome.com/kevin