[w3c/webcomponents] Considering Shader Module Types (#853)

Shaders are loaded in WebGL in the browser by passing the shader source code string through JS (https://developer.mozilla.org/en-US/docs/Web/API/WebGLShader).

If we could extend module types to handle shader loading, it seems like module types would work out very naturally and directly for shader loading use cases as another language that runs on the web.

While we are considering the different module types, I wanted to mention this possibility as another data point to consider when it comes to the security and shape of the sorts of integrations we might expect here. The list of all possible module types for the web probably isn't more than 10, let alone what will be implemented. So understanding the use case examples, and what general thoughts are on them, can only help.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/webcomponents/issues/853

Received on Monday, 11 November 2019 22:47:48 UTC