39 ms·
Does this diminish the results of all browsers shipping decent WebGL 2.0 support, though?
by royjacobs 5y ago
Does this diminish the results of all browsers shipping decent WebGL 2.0 support, though?
- fsloth 5y agoIt implies industry has little interest in actually supporting it. A GPU debugger is a critical tool in modern GPU development. Maybe they are holding on webgpu. People are carefully optimistic in it becoming the one API to be actually cross-platform.
- royjacobs 5y agoMaybe. It's not like the market for native graphical debugging tools is overflowing with options either, which is why I didn't understand OP's point that well. Additionally, with some careful coding you can already run WASM+WebGPU applications both natively (e.g. via wgpu-rs) and in the browser, so you can pick and choose the best tooling depending on your use case, so ultimately I guess that's going to be the way forward.
- jcelerier 5y ago> People are carefully optimistic in it becoming the one API to be actually cross-platform. idk I'm shipping code that uses the Qt RHI which works on D3D, GL, Metal, Vk ... cross-platform enough for me.
- pjmlp 5y agoBesides what fsloth replied, it is also 10 years too late, WebGL 2.0 is a subset of GL ES 3.0, released in 2010. So in 10 years, no browser vendor ever thought it was worthwhile improving their developer tools to support 3D developers. Firefox did have a toy debugger that they eventually killed and that was it.
- mrdoob2 5y agoSafari did.