A while ago I did contribute to p5.js, but my two simple bug fixes each took 5 months to make it into a release. That pace of development is just too slow for me personally. I got upset with TPF staff and they banned me. Yet even if that didn't happen, I wouldn't have been happy with making a few improvements to p5's documentation. I wanted to start from scratch and take an entirely different approach.
I also don't want to contribute to p5.js anyway because TPF betrayed co-founder Ben Fry and basically stole his own project from him.
I agree that the p5.js website as well as documentation could be improved. But why not contribute to the original project instead of forking it?
A while ago I did contribute to p5.js, but my two simple bug fixes each took 5 months to make it into a release. That pace of development is just too slow for me personally. I got upset with TPF staff and they banned me. Yet even if that didn't happen, I wouldn't have been happy with making a few improvements to p5's documentation. I wanted to start from scratch and take an entirely different approach.
I also don't want to contribute to p5.js anyway because TPF betrayed co-founder Ben Fry and basically stole his own project from him.
https://q5js.substack.com/i/152794191/my-beef-with-the-processing-foundation
hmm, i see, thanks for the answer!
When will you have FFT analysis in Q5?
Is FFT analysis part of p5.sound? You can already use p5 libraries like p5.sound with q5.js!
Are there docs that mention this?
It's on the first section of the homepage.
Hmm. Can I suggest a proper section for this?
Like a separate section?
Yup, in the Learn area. A small one liner on the homepage is easily missed.