2 ms·
The way I see it, browsers are already API-bloated. I just don’t see the justification for further developing a graphics API when another one based on more mode
by danielvaughn 5y ago
The way I see it, browsers are already API-bloated. I just don’t see the justification for further developing a graphics API when another one based on more modern standards is already underway. It’s not like it’s a small effort.
- debugnik 5y agoIf it took 10 years to achieve widespread webgl 2 support it could take another 10 for webgpu. People want to make web applications today, not plan them for the future.
- modeless 5y agoWebGL 2 was fully developed five years ago. What happened now was Safari finally exposed support, and reused a lot of implementation effort done by Google in the form of ANGLE (which Safari was already using, just not exposing WebGL 2). This was not a from-scratch implementation and development of a new API, it was a collaboration and adoption of an existing API shipped in all other major browsers for years. The Metal ANGLE backend work done by Apple was a large chunk of work, but a lot of it needed to be done anyway to continue to support WebGL at all on Apple platforms given Apple's deprecation of OpenGL.