5 ms·
I think their effort would be much useful, if they focus on WebCL. It is already standardized (unlike their "SIMD" object). CPU implementation of WebCL, that ut
by IvanK_net 12y ago
I think their effort would be much useful, if they focus on WebCL. It is already standardized (unlike their "SIMD" object). CPU implementation of WebCL, that utilizes SIMD, would probably offer much better performance, than any current Javascript engine.
- azakai 12y agoWebCL is not yet standardized, there is still ongoing discussion about that last I heard. In any case, the two are not mutually exclusive, different people are working on each.
- IvanK_net 12y agoThe version 1.0.0 was standardized in March 2014 - https://www.khronos.org/registry/webcl/specs/1.0.0/ https://www.khronos.org/registry/webcl/specs/1.0.0/
- azakai 12y agoOh, interesting, I wasn't aware of that! Do you know what the implementation status and intention to implement is, among browsers?
- IvanK_net 12y agoWebCL implementations for Firefox and Chromium exist for 2 years. But they have not been included in any alpha, beta or canary release. Browser developers don't seem to care about WebCL, but they do care about WebGL, which is strange. Samsung made it work in Tizen, but sadly, it is not very widespread OS. https://www.youtube.com/watch?v=TurCVdaUTMY https://www.youtube.com/watch?v=TurCVdaUTMY
- fulafel 12y agoWebCL community is geared towards exposing platform OpenCL backed by GPU, that would be stealing their fire. Though it might still be the smartest thing to do given the poor state and lack of recent progress of GPU OpenCL drivers. Even desktop apps that would like to use OpenCL are just barely limping along. See eg. Blender.
- IvanK_net 12y agoI agree, even CPU implementation of WebCL could be much faster, than the fastest JS engine (because it is low-level C code). Currently there are several very good OpenCL implementations, running on the CPU. BTW. GPUs use SIMD too :)