[foota]

OpenGL (which WebGL is a sister API of) is a relatively obnoxious API to work with, requiring lots of calls to set an maintain state, as well as pick which state you're working with for a give call. (conceptually you can think of there as being a bunch of static variables that point to the current state for a call). This is IMO one of the biggest barriers to OpenGL, although I believe they've made some of this more explicit than it used to be.

It looks like this API aims to keep the same abstraction level as OpenGLs API, but without the state management required.

So this won't allow you to go straight to OpenGL, but it will teach you the concepts and objects you use with OpenGL.

One of my favorite tutorials and references for learning graphics concepts is http://learnwebgl.brown37.net/.

[pjmlp]

Picogl, threejs or Babylonjs would have been better choices, given their usage across WebGL community.

[foota]

Picogl looks like you still have to manage state, whereas ThreeJs and BabylonJs are both fairly high level iirc?

Seems like the framework used in the tutorial is somewhat in between, where you're still using opengl concepts but without having to do state management.