> That way people will have completely portable code.
Makes sense about portability, but what is your security model? Are you using static analysis, sandboxing like NaCl, or something else?
Makes sense about portability, but what is your security model? Are you using static analysis, sandboxing like NaCl, or something else?
We don't give pointers, and we do things client-side like guarded arrays (not necessary on the server). Memory management is handled by the core. I will get our guys to put a post up that covers KL in more detail - security was a major consideration for us.
There are more details on KL, and the reasoning why we didn't use JavaScript
While I have you here :) , can you please elaborate on your Bullet/Fabric demo? Specifically, how did you get the Bullet C++ code to run on the Fabric Engine? (Since that doesn't use C++?)
Does that answer your question properly? I can get more info if needed.
I asked because I work on compiling C++ into JavaScript, and I was curious if your technology included something to compile C++ into KL.
I assume integrating existing C++ libraries to Fabric Engine has no security model, then?