Message from JavaScript discussions

October 2018

— Consider if you will Golang concurrency thread model of M:N

— 

Now consider that each thread in the system is actually a dedicated server CPU core, rather than multiple threads in a pool

— How to use it?

— In this way every CPU core receives exactly one combination of an instruction token and a data token, in the form of a single instruction stream

Message permanent page

— So if you have 64 cores in your server CPU, you can send 64 individual instruction streams to that server simultaneously

Message permanent page

— I need only one more

— And it will arbitrarily execute them, and transmit the result through the network, most likely to a central master mainframe, which will the multiplex the outgoing and incoming data, so that it is given context and manipulated in the way the user desires

Message permanent page

— This is kind of large architecture, however in fact it is an abstraction of much smaller, discrete, and simple systems, simply scaled way up

Message permanent page

— You say "simple" too much, but i dont see it🤤

— It is essentially, a massively parallel JavaScript super computer system, a network based supercomputer composed of many individual subsystems, each of which is it’s own computer, you could also call it a clustered super computer

Message permanent page

— Whoever thought we could ever develop the technology necessary to even make a JavaScript super computer?

Message permanent page

— It is crazy, however my comparatively small advancements have made all of this possible, easily technically feasible even

Message permanent page