Message from JavaScript discussions

October 2018

— You have to tell it to do this manually at every step

— 

Manually write these pathways up and out of code, so that your control flow can transfer to a different stack

— It is a mess, that has been completely abandoned since the 1990s

— And JS developers who are using these generators to write concurrent code are really only making these tiny little functions with very tiny responsibilities, because if they make it any larger the technical debt balloons out of control

Message permanent page

— Essentially, the technical debt makes it nearly useless in JavaScript

— All my technology does is offload that same exact technical debt, without actually changing it, and just makes it so that the developer never has to deal with it themselves

Message permanent page

— HzScript programs are extremely massive in size compared to their original src, many times the original size

Message permanent page

— And they will run slower, good lord the performance impact will be massive, because it will be impacted at every single step of execution

Message permanent page

— I may be solving the problems of concurrency, but it still remains within the limitations of the virtual machine itself, hobbling my efforts at every turn

Message permanent page

— It is a virtual concurrency, not at all supported by the language runtime, and only implemented using the standard control flow mechanisms provided by that runtime, which were never really designed to be used this extensively

Message permanent page

— I had to kill the native stack because of how horribly it affected the concept of concurrency in this system, even...

Message permanent page

— Was a O(n) context switch (n = stack.length), jitter to high heaven and memory thrashing, massive amounts of heap allocation... without the native stack it is O(1) with very little heap allocation and only one single index that the native stack can grow/shrink

Message permanent page