Decision Record?

Hi all,

First off, just want to say great work with the spec. I've been experimenting with WebGPU more lately, and it's a HUGE ergonomics upgrade from WebGL. I'm finding it a joy to use (and I don't think I've ever said that about a graphics API).

One thing I've found challenging as I'm on-boarding to WebGPU is understanding why some functionality I'm used to in WebGL doesn't exist in the new API. Recent examples:

- Why can't the API generate mipmaps for me? Found the answer [here](https://github.com/gpuweb/gpuweb/issues/386).
- My can't I time a set of arbitrary commands on the GPU? Found answers [here](https://github.com/gpuweb/gpuweb/issues/2046) and [here](https://github.com/gpuweb/gpuweb/wiki/GPU-Web-2023-11-08#problem-measuring-time-deltas-with-writetimestamp-3952).

As you can see, the answers I wanted are available, but can be obscure and require parsing long conversations. I'm wondering if the working group would consider maintaining a sort of decision record or FAQ of more substantial or controversial departures from WebGL and the reasoning behind them, maybe even just with links out to relevant meeting minutes or GitHub issues. I've found the [WebGPU from WebGL](https://webgpufundamentals.org/webgpu/lessons/webgpu-from-webgl.html) article on WebGPU Fundamentals extremely helpful as a starting point, but it doesn't provide reasons for the differences, which I think are valuable to anyone who wants to be a serious practitioner. I also feel a document like that could be of immense value to the real-time graphics community as a whole, since your research seems to be uncovering a lot of interesting details about the intersection of the current set of native graphics APIs.

Best,

Tarek Sherif
http://tareksherif.net/