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

Re: [Public WebGL] another proposal to temporarily expose some device/driver information only when really needed

On Tue, May 1, 2012 at 8:22 PM, Benoit Jacob <bjacob@mozilla.com> wrote:
I'm a bit hazy as to how that profile object thing would be updated. Also isn't it a problem if some capability issue is indicated by the profile object, which then some app developer jumps on, and later that is deemed "resolved", despite it not being resolved for that particular app developer, and suddenly his app's crashing machines again. Furthermore, assume some compatibility test is made by an app developer, and then the issue is deemed resolved, but later the same issue string is exposed again, the app flip-flops between working and not working for some people, without any real control of the app developer.

I think issue profiling is extremely important to deploying WebGL apps. Here's a scenario: Someone makes some game in webgl which for some or another reason turns out to be hugely popular. They go from zilch to 50 million users overnight. Now some percentage of that users will get issues, say 2%, imagine getting a million support requests over night, and having no clue whatsoever what to tell users...