Message from JavaScript discussions
December 2018
— Hmmm
If I could boil it down... I would say that my thing takes the call stack and dumps it into the heap
— In almost every way
— Then, once it's there, I have code manipulate the heap
— It probably makes the GC cry tears
— Its readable🤤 okay i can understand what examples do, but.. automatic thing is a head blow💀 and there should be motivation story imo, some realworld application example like some computation in parallel and then its application
— My realworld example... I always had some idea of using WebGL
— In WebGL, you call 1 function per frame of animation/rendering
— So... where renderN is a loop which repeatedly calls the render function:
spawn render1();
spawn render2();
spawn render3();
— WebGL will run at about 200FPS
— As i work in browser only i can find some use case there, but you describe the server case, right
— So, 200 / 3 FPS per rendering frame