Message from JavaScript discussions

October 2018

— So you can scale up a randomness pool if an app needs lots of random


Yeah, anywhere a function appears will be recompiled, and will also have that special subroutine adapter just in case it gets called by something that is not a dispatcher

— I mean, the one where all functions are capable of starting their own dispatcher

— That is a failure state in most cases, because it is a point at which you are not able to utilize any sort of interruption, as the dispatcher is unreachable at that point, and there is no clear path to return control to anything upon an interruption

Message permanent page

— So I am wondering, how many of those will bump into that issue, and how much of a problem Proxy will be

Message permanent page

— In general, it may just break the whole damn thing

— Use a small c++ loader to inject the built-ins from node

— And that's it

— It does not make sense to reimplement all

— It's better to maintain a small .node file with crossplstform c++ code and integration with v8

— The problem is reachability of a callback

— Most C++ code invokes JS directly