3 ms·
Based on my interests, I tend to look at this in the opposite direction. Vulkan is the correct level of abstraction for an API targeting high performance utiliz
by throwaway17_17 7y ago
Based on my interests, I tend to look at this in the opposite direction. Vulkan is the correct level of abstraction for an API targeting high performance utilization of CPU/GPU rendering/compute resources. But I don't do any web based programming (other than pushing results of large data formatting to simple forms for my office). I don't care what uses a front or back end dev finds simple or low-boiler-plate, I want maximum control with as much cross-platform portability as possible. But I do get that other developers want something different. So I'm all for Khronos staying away from WebGPU and focusing on the things I care about.
- rafaelvasco 7y agoYeah, there are both use cases. Having a low level, very flexible API and a higher level, more opinionated and probably easier to use API. Having only one doesn't cut it in my opinion. There must be two levels of use.