On Wed, May 7, 2014 at 4:40 PM, Vladimir Vukicevic <vladim...@gmail.com> wrote: > WebGL made an explicit decision to do things this way -- the one thing that I > would go back and change is getExtension() returning an extension object, > instead of acting as an enableExtension(). I don't remember *why* we did > this, but I seem to recall some decent arguments for it.
At least with the enable approach you can later phase out the necessity for the call entirely by enabling widely deployed extensions for everyone. Currently you end up with a tower of classes and a matrix of extensions that you will have to support indefinitely. It's still not clear to me why developers would be more careful about hardware differences than they are with browser differences though. It seems by-and-large the same problem. We hit issues with Firefox OS all the time with people not having tested with it. > There really isn't a good solution to this problem in general. The Web has > tried multiple things, including the WebGL approach. All of them have a set > of upsides and downsides; there isn't a perfect option. We have learned repeatedly that mode switches are especially bad and that there's better alternatives. Even if there's no perfect option, we can do better than bad. -- http://annevankesteren.nl/ _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
