GPU-accelerated Path Rendering (2012) [pdf]
graphics.rwth-aachen.de
graphics.rwth-aachen.de
NVidia's technology to do this has been around for years, but it hasn't 'taken off', I've yet to see anyone use it (maybe Adobe Illustrator uses it?). Khronos (the group who created OpenGL) even has a standard for accelerated vector graphics, called OpenVG, which has also been around for years as well yet only the Raspberry Pi and a few other embedded ARM devices seem to support it.
My conclusion? Path rendering is insanely useful, but it's very complex for both application developers ("this is slow and hard") and artists alike ("I hate these weird grabby-handles!"). That complexity comes at a cost, and time after time we've been shown that complexity is often overpowered by simplicity even when it's inferior (bitmap images).
I would like to see Quadratic (i.e. a bezier curve with just one control point) become popular due to their artistic simplicity as well as their easy relation to graphics hardware (a triangle with a simple GLSLfragment shader can render a quadratic bezier curve).
Perhaps quadratic bezier curves aren't as mathematically pure (cannot represent circles "perfectly") -- but they are artistically beautiful and, in my mind, just as useful as pixels are (in real-time applications). http://imgur.com/a/i2RtE
I'm excited to see where accelerated path rendering goes in the future. In conjunction with distance field rendering, it's absolutely fantastic.
Yep: http://blogs.nvidia.com/blog/2014/06/23/two-steps-adobe-illu...
Quadratic bezier curves, unlike cubic ones, do actually map really well onto GPUs (given their basis on triangles) quite unlike what you've said here.
In addition I would guess webgl would get around 10% performance vs native because it is missing a lot of useful API for that kind of stuff and has a significant overhead in javascript - rendering vectors needs a lot of CPU work and not having floats (only doubles) does hurt in use cases like bulk geometry.