[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Public WebGL] WebVulkan
To get a bit more specific on top of Justin's comments: Vulkan exclusively uses memory mapping as it's mechanism for updating allocated buffers. Because of the security restrictions that Justin mentioned you will never
(Okay, maybe technically Brendan Eich decided this? The be fair I doubt he was thinking of high performance GPU interfaces at the time.)
We CAN replace Vulkan's memory mapping with a BufferSubData-like interface, and probably simplify a few things in the process. (At that point you could hide copies to GPU memory if you wanted to.) But then we've lost the 1:1 mapping, so it seems silly to me to not take advantage of that fact to try and make the rest of the interface more web friendly.