RFC For a VSCode PDE

Hello @moon,

I fully support the Enhancement details in the RFC.

It is my understanding that the RFC prototype is a fork of the open‑source VS Code codebase combined with the Processing core, Java and App with the potential for better future integration with a modular approach.

I would also like to see the decoupling of the CLI so that it can easily be integrated with other code editors of my choice.

The RFC states:

The Processing CLI currently requires the whole PDE to already be installed on the user’s computer, so we’ll want to work toward making the CLI standalone to remove the dependency on the current PDE implementation.

processing4/BUILD.md at main · processing/processing4 · GitHub
states:

Processing consists of three main components: Core, Java, and App. The Core is independent, while Java and App depend on it. Currently, Java and App are interdependent, but efforts are underway to decouple them.

Google Gemini interaction:

If the Processing core and CLI are isolated into separate, downloadable modules under the LGPL (or a similarly structured copyleft license), a VS Code fork released under a permissive license (like MIT) can pull them in dynamically without triggering license contamination.

As long as the VSCode fork interacts with the core/CLI via a clean separation, such as standard CLI process calls, IPC, or dynamic linking, the permissive editor code and the copyleft processing runtime remain legally distinct.

Go for it!

References:
Visual Studio Code - Wikipedia

:)