This.. may be a very weird and potentially bad idea, but I thought i'd put it up here for consideration. Most (if not all) WebGL contexts as I understand it supports compiling (and using) GLSL.
GLSL (based on C) has simple primitive types (minus strings), for, while, do and conditional branching. Only gotcha is recursive calls isn't permitted, which i'm unsure if its all that too big of an issue. With that said it seems like it might be a good way of pushing off array buffs on the heap into GL as a texture (while sharing it) and processing "thread-like" modules (obviously limited in functionality). I know there's been work with OpenCL to try and bring that capability with GLSL into javascript, i'm just curious if anyone had any insights here. According to GLSL/WebGL spec maximum texture size + shader program is 2000x2000x4 (or roughly 15MB) -- You received this message because you are subscribed to the Google Groups "emscripten-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
