[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Public WebGL] EXT_shader_texture_lod in WebGL2?
Writing multiple renderpaths for multiple versions, that take full advantage of the capabilities of each version is very time-consuming and difficult.
The easiest way to for developers to take full advantage of WebGL2 for the time being, would be to be able to "polyfill" features they'd like to use into WebGL1 that are found in WebGL2.
By abandoning WebGL1, with a very fragmentary capability coverage to WebGL2, you're ensuring that WebGL2 adoption will be much slower than we all wish. That's because there's no easy way to "polyfill" the enticing features of WebGL2 into WebGL1. Although I don't think this should prompt a mass backporting effort, I do think this warrants continued effort to improve the existing WebGL1 capabilities across all UAs and maybe introduce more WebGL1 extensions for particularly sore spots (like 3D textures).