Is your feature request related to a problem? Please describe.
it's backwards compatible as far as I know so we shouldn't have to change much, the only hiccup is with shaders, since we don't have attribute and varying anymore, they're a combination of in and out, as well as needing the shader to start with "#version 300 es\n..."
Any more information?
WebGL 2 has vertex array objects support, it might improve performance
if we don't want to go around breaking everyone's shaders in v5000 we can still try VAOs by getting the extension OES_vertex_array_object
Is your feature request related to a problem? Please describe.
it's backwards compatible as far as I know so we shouldn't have to change much, the only hiccup is with shaders, since we don't have
attributeandvaryinganymore, they're a combination ofinandout, as well as needing the shader to start with"#version 300 es\n..."Any more information?
WebGL 2 has vertex array objects support, it might improve performance
if we don't want to go around breaking everyone's shaders in v5000 we can still try VAOs by getting the extension
OES_vertex_array_object