Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Plans for WebGL 2 #23

Open
ignishub opened this issue Feb 11, 2017 · 3 comments
Open

Plans for WebGL 2 #23

ignishub opened this issue Feb 11, 2017 · 3 comments
Labels

Comments

@ignishub
Copy link

Is there any plans for WebGL 2?

@dmitshur
Copy link
Member

I don't have immediate plans to work on this, but goxjs/gl could support it one day (probably not very soon).

WebGL 2.0 is very new and there are some browsers that don't support it yet. See http://caniuse.com/#feat=webgl2.

image

So it'd have to be an optional backend, with a fallback.

How does its API compare? I'm not familiar with it yet. Is it purely additive, or are there incompatible changes?

To make this happen, I expect the very first step would be to create pure WebGL 2.0 bindings (e.g., similar to https://github.com/gopherjs/webgl, but target WebGL 2.0 instead of 1.0). After that's done, we can consider upgrading goxjs/gl browser support.

@dmitshur
Copy link
Member

How does its API compare? I'm not familiar with it yet. Is it purely additive, or are there incompatible changes?

I've looked at https://www.khronos.org/registry/webgl/specs/latest/2.0/#4.1. It's mostly an addition to the WebGL 1.0 API, with some minor backwards incompatible changes.

WebGL 1.0 mapped to OpenGL ES 2.0, while WebGL 2.0 maps to OpenGL ES 3.0.

@ignishub
Copy link
Author

Thanks for your answer! =)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants