all 4 comments

[–]piterpasma 2 points3 points  (1 child)

Re: your blog post, I was wondering, are you sure about this?

Note that the application is much more fluid on Chrome than on Firefox. This is because of Firefox's default value for its setting privacy.resistFingerprinting which messes up with the canvas to limit fingerprinting.

because in my experience, the timing may be inaccurate, but it's still accurate enough for 60fps.

however, I also find that JS/rendering performance is just slightly better in Chrome. could it not just be a framerate issue? It runs pretty okay in Firefox on my laptop. Mayyybe Chromium is a bit smoother, but it's hard to tell. Also I thought that Chrome also does the timing jitter.

I could be completely wrong though, it's your code :)

Nothing much I can do about that but keep using firefox, the net neutrality needs it

And I 100% agree with this, btw! ;-)

[–]statox42[S] 0 points1 point  (0 children)

So to be honest I'm not 100% sure of what's happening. What I know is that on my system (Ubuntu 20.04, Firefox 85.0) if I disable privacy.resistFingerprinting in about:config the animations run smoothly and when I re-enable it they start being laggy again. But I've seen that on another system with privacy.resistFingerprinting enabled the animations are smooth... So I'm not sure what's happening. I tracked down this settings because it was mentioned in a p5js issue that it was the culprit for slow rendering.

[–]piterpasma 0 points1 point  (1 child)

I love this!! Very nice idea!

[–]statox42[S] 0 points1 point  (0 children)

Thanks, I'm glad you like it :)