Bringing the web up to speed with WebAssembly

Re:Bringing the web up to speed with WebAssembly by lj3 on Friday September 22, 2017 @05:11PM (#15315836)

Maybe. OpenGL has a lot of history and baggage. I'm pretty sure the current browser engines don't use OpenGL for 2d graphics. I think they still use Skia (Chrome) and Cairo (WebKit). It could be as "easy" as allowing calls to be made directly to those graphics libraries in WebAssembly.

[ Parent | on HN ]

Re:Bringing the web up to speed with WebAssembly by pjmlp on Saturday September 23, 2017 @03:30AM (#15318656)

Skia makes use of OpenGL, DirectX or Vulkan.

[ Parent | on HN ]

Re:Bringing the web up to speed with WebAssembly by amelius on Friday September 22, 2017 @05:52PM (#15316182)

In any case, it should be hierarchical. It should be simple and efficient to move an object and all its children around.

[ Parent | on HN ]

Re:Bringing the web up to speed with WebAssembly by lj3 on Friday September 22, 2017 @06:13PM (#15316354)

I think you're missing the point. An object and child hierarchy is too high level for what I'm suggesting. Just expose the graphics library and let the programmers handle the rest. If you want something hierarchical that's simple and efficient to move an object and all its children around, great. You write that for your applications. Make it into a framework if others want to use it. But if somebody wants to use a different approach for their application, they should be able to do so.

[ Parent | on HN ]

Re:Bringing the web up to speed with WebAssembly by amelius on Friday September 22, 2017 @06:25PM (#15316445)

Well, I'm all for a low level approach. But going a little higher allows the GPU to handle a lot of things. Or do you propose to incorporate something like CUDA/OpenCL into WASM?

[ Parent | on HN ]

Re:Bringing the web up to speed with WebAssembly by perilunar on Saturday September 23, 2017 @09:26AM (#15319617)

SVG perhaps?

[ Parent | on HN ]