3 ms·
That actually doesn't quite solve the problem as we disallow dynamic code evaluation. This is for a couple reasons: * Security: In case of an attack we need to
by kentonv 8y ago
That actually doesn't quite solve the problem as we disallow dynamic code evaluation. This is for a couple reasons:
* Security: In case of an attack we need to be able to call up the code to do forensics, which is hard if it was downloaded dynamically at runtime.
* Optimizations: We want to keep the ability to pre-compile code e.g. into V8 code cache format before distributing it to the edge.
- buu700 8y agoAh, I thought that might've been part of it since you brought up the comparison to eval; just wanted to clarify that there are other options for avoiding reliance on external subresources. which is hard if it was downloaded dynamically at runtime Not sure if you mean something other than what this sounds like (I haven't used CF Workers), but just to clarify further, the option I mentioned causes emscripten to emit one single JS file with no external code downloaded at run time. (In any case, that performance optimization alone certainly sounds like a good reason for the separation.)