6 ms·
I hadn't heard of about half of these - it's great that there's a sort of directory for them. Sweet.js is pretty awesome (I was going to say it's sweet, but th
by thomasfoster96 12y ago
I hadn't heard of about half of these - it's great that there's a sort of directory for them.
Sweet.js is pretty awesome (I was going to say it's sweet, but that's stupid). Broadway.js and Shumway look pretty awesome, I'm going to check them out tonight.
Regarding Parallel JavaScript, does anyone know how this relates to Khronos' WebCL project? Hardware manufacturers seem really interested in WebCL, but software developers aren't.
- derf_ 12y agoUnlike OpenGL, OpenCL allows writes to arbitrary addresses computed by the OpenCL kernel. To be safely run on the web, you have to solve a very difficult validation problem to prove that an arbitrary kernel won't do bad things. I don't think anyone has adequately solved that problem. As stated at <https://bugzilla.mozilla.org/show_bug.cgi?id=664147#c30> https://bugzilla.mozilla.org/show_bug.cgi?id=664147#c30>, "The future for GPU compute in Firefox is ARB_compute_shader, which is now part of ES 3.1."
- thomasfoster96 12y agoYep, I'd heard browsers wanted to use Shaders instead of WebCL. I think there's a couple of node packages that implement WebCL, but they're not in the browser environment and they're really only used with trusted code. Looking through some discussions on Google Groups related to chromium development, it looks like they thought WebCL might be safe to use eventually, but not in the near term.