Frame rate, rendering and performance

[mark4sisb]

@ego-lay_atman-bay

That's not true, snap runs multiple loops simultaneously, as in, one block in one loop, another block in another loop, then the next block in the first loop, then the next block in the second loop/ and so on.

@bh

Alas, Snap!'s scheduler doesn't do real time slicing; it relies on explicit yields that Snap! carries out at the bottom of every loop iteration. So if the first script doesn't have any loop blocks (for example, it uses recursion instead) it'll win the race even if it actually takes more time than the second script.

@bh has said things like this in multiple previous posts; such was my source. It could be wrong or outdated, however.