You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It is increasingly hard to use a single uniform compatible declaration for both WebGL 1 and 2 features (extensions, textures, UBO etc.). While WebGL2 achieving pervasive support now, would it be nice to have standalone package for WebGL2 only?
The text was updated successfully, but these errors were encountered:
stwind
changed the title
[webgl2] A separate package
[webgl2] A separate package?
Feb 10, 2022
Yeah, the moment has finally come for WebGL2. Instead of separating v2 I'd propose to extract the legacy v1 stuff into own package... What are your thoughts?
Yeah extracting legacy stuffs to its own package seems to be a better idea.
I am not quite sure how to do that yet, since there will be quite some overlaps/similarities between them. And as the "new" webgl package keep evolving to be more WebGL2, some common parts will almost eventually break for the legacy webgl1 package.
So I think the problem will be like how much or what should be kept in a common package, if any? Obviously the gl constants is the safest one to keep as common.
It is increasingly hard to use a single uniform compatible declaration for both WebGL 1 and 2 features (extensions, textures, UBO etc.). While WebGL2 achieving pervasive support now, would it be nice to have standalone package for WebGL2 only?
The text was updated successfully, but these errors were encountered: