RFC: When does libprocessing stop being R&D

RFC

I've received a question around when libprocessing moves out of the Research and Development phase

I think this is an important question that I've failed to give a clear answer around. This is because the honest answer was always "I don't really know."

The reason this project exists at all is because Processing4 so for one thing: I would like to see that we are actually able to use libprocessing inside of the PDE.

Additionally, we are making big promises around being able to use modern rendering techniques. Something else that would prove the point is being able to do a compute shader inside of the PDE.

Last thing I want to say is that, one of the big benefits of Rust, and using Bevy is that we are able to compile to WASM. So is this is something that p5.js would be able to use?

We have shown considerable promise with mewnala and @SableRaf has been making really great progress with porting Processing examples to mewnala. Most importantly he is talented at QA and it's been helping us catch many edge cases.

What does everyone think in terms of these milestones?

• libprocessing in PDE
• compute shaders implemented in PDE
• p5.js as a possible endpoint? (Maybe this shouldn't be a blocker, but it's certainly a question that needs to be answered)

Lastly, just to remind us about the FP Texture issues beautifully documented by @tychedelia https://github.com/processing/processing4/issues/1324 which have also been a problem for some time now: https://github.com/processing/processing4/issues/724

helps push us towards making a Processing 5.0 milestone (which I will make an RFC for soon). After meeting with folks from LibreGraphicsMeeting and learning more about the Processing-java (and not p5js) community I can see much more clearly, and want to keep getting rooted in this.

Revise os marcos propostos para libprocessing-in-PDE, compute-shader e p5.js/WASM, juntamente com o trabalho relacionado de Processing4 e processing-examples-mewnala. Considera-se concluído quando o projeto tiver concordado com marcos concretos e definido quando libprocessing deixa a R&D; este RFC não identifica arquivos de implementação nem testes.