One problem that I can see, is the fact that some scripts require information from previous sections of the same script in order to work properly, and if multi-threading was introduced, there would have to be a way of controlling what thread was run when, so that all of the required information was available.
Yeah, I also thought about this, I didnt spend too long on the
thought but I chalked it up to being a standard that would be
need designed. I think it might just be a matter of
synchronization, but I think there might be different ways of
setting it up, so I'll just wait for an expert to speak up.
While it's not exactly the same thing, currently you can have multiple scripts running at the same time, and they work just fine (of course the longer and more complicated the script, the longer it's going to take to run).
and as its known you can have multiple scripts, but they
all run sequentially in order, and not simultaneously. the
multi-thread approach is what i believe to be a matter of
shotgunning your code, getting more out of your spare cpu cycles.
