Hello, thanks for the insights. One question, does that imply that a timer jitter implementation causes that overhead? I think timer jitters have been introduced to JavaScript's performance.now() on all modern browsers several months ago as a reaction to Spectre, I cannot imagine that caused similar performance problems there, or a lot of websites would have suffered. Or what about invoking a low-resolution OS timer instead? (just some guesses without knowing implementation internals, so I might be wrong here) Scratch is probably the largest user community using Flash those days (close to 30 million users). Wouldn't it have been an option to run an internal performance test together with the Scratch team before releasing such a breaking change? Thank you!
... View more
AdChoices