PSA! Using the p5.js web editor is not recommended

[quinton-ashley]

I've had several users report major problems with the p5.js web editor! ⚠️

But note that p5play is not affiliated with the Processing Foundation, in fact I've become quite disappointed with their leadership lately. Unfortunately, it seems they are unwilling or unable to fix critical issues, some of which are several years old. These issues make the p5.js web editor unreliable and inadequate for p5play users.

1. When console.log is used to print a number on
   every frame, it causes drops in frame rate.
   This makes the p5.js web editor unusable
   for play testing.

2. console.log doesn't print out the correct
   values of arrays before and after they're
   changed.

3. The sequence mode of loadAnimation doesn't
   work unless you use backticks for the name
   of the image file.

I recommend using OpenProcessing or any other online code editor instead!

If you find any other issues with the p5.js web editor, please leave a comment here because the Processing Foundation closes important issues that they won't fix.