Obsidian has been published as a possible proposal for WebGL-Next. As we reported a few days ago, The Khronos Group now has a staging area for WebGL-Next proposals and just a few minutes ago was the first proposal submitted.
Mozilla developers have been working on Obsidian and is explained by their documentation as:
This is Mozilla's draft proposal for the GPU API for the Web, called Obsidian. It is a low-level API that provides maximum feature set of the GPU to the web applications. The API is designed for WebAssembly, modern GPUs, and multi-threaded environment in mind.
Obsidian is a temporary code name, signifying the Vulkan roots of the API: Obsidian is a naturally occurring volcanic glass formed as an extrusive igneous rock.
This proposal is not a specification. It includes reasoning for the design decisions, draft WebIDL and a bit of example code. We don't aim to provide a complete specification, instead we want this proposal to represent our vision of the future API in the working group discussions, a vision of rich graphics on the Web powered by a low-level explicit API.
The need for a more efficient graphics API for the Web is clear. What is not clear is the look and design of such API. Previous mailing lists discussions were split into two groups: one that considered Metal as a good baseline for the new API, due to it simpler and higher level abstraction, which is easier to provide safely on the Web. Another group saw Vulkan as an ultimately portable API that just needs to be re-defined on the Web with some feature cuts.