I think the original post refers to WebGPU
given that WebGL was known to use an "old" approach even before it was released and we don't have the problem with WebGPU I hope history doesn't repeats itself
In practice it'll only use Vulkan on Android and Linux, the main two implementations both use DX12 on Windows even though Vulkan is technically usable there.
PBO support in WebGL lacks glMapBufferRange for non blocking read back.
All we need is the last mile -- progressive web apps -- to include better support for integration with desktop OSes and we have a way to take WASM apps and drag them to the desktop.
The up and coming languages for writing these WASM apps seem to be Go and Rust. Here's a Rust example:
https://github.com/gfx-rs/wgpu
https://dawn.googlesource.com/dawn
Some non-browser WASM runtimes also have WebGPU support already, but unfortunately only for offscreen rendering or compute tasks (e.g. for writing cross-platform windowed apps as WASM blobs, there's a window system glue layer missing).
I fully agree with that, for a lot of use cases WebGL has everything you need, means it has the potential to become the cross platform graphics API OpenGL dreamed to be. And as a bonus you have a realistic way to run whatever app you are writing in the browser with WASM+WebGL.
I just think for AAA games Vulcan, Metal and DirectX12 will probably still be the way to go. But GUI libraries? Less highest end games? There is just no point once you can use WebGL everywhere. And then if you want to have a browser Demo you have a realistic chance to get it.