Scratch

Nah, 1s1s just shows programming awepicness. 

I suppose you could avoid forever-loop-sync problems like this by designing a project as 1s1s. But then again you could do exactly the same implementing a updating cycle like this:

when gf clicked
forever
    set [timer_init v] to (timer)
    broadcast [update v] and wait
    broadcast [render v] and wait
    repeat until <((timer_init) - (timer)) > ([1] / [60])> //60 FPS
        wait [0] secs
    end
end

(I haven't tried it myself; read it from someone in these forums)

_________________
Yay for new posts while previewing    As Magnie said, it's way better to manage similar sprites as one sprite that is stamped.

s_federici wrote:

Scratch lists are much slower than handling sprites (and you need lists to store all the necessary information), in the end multiple sprites are faster than 1S1S.

Unfortunately, this isn't good for me when I have to show why the majority of programming languages are heavily 1S1S (1 thread) and not based on multiple threads instead...