The Processing Foundation announced on November 9 that Anthropic has joined its Development Fund as a Titanium Tier supporter — the fund’s top donation level — earmarked for finishing the milestones toward Processing 5.0. The centerpiece of that work is libprocessing, an experimental reimplementation of the Processing API written in Rust, intended to eventually power Processing Java, Processing Python, and browser-based tools from one shared core rather than three separately maintained ones.
Why a Rust core, and why now
Processing’s existing implementations have grown somewhat independently over two decades — the Java edition, the Python mode, and p5.js each reimplement overlapping pieces of the same drawing API in a different language. libprocessing’s pitch is to collapse that duplication into a single Rust library that the other editions call into, either directly, through a foreign-function interface, or compiled to WebAssembly for the browser. The Foundation’s own announcement frames the motivation plainly: a “safer, more robust technical base to support visual thinkers and creative coders into the next era.”
The project has been developed openly since around October 2025, and shaped by community feedback at FOSDEM, RustWeek, the Libre Graphics Meeting, SIGGRAPH, Processing Community Days in New York and San Francisco, the Processing Discord, and GitHub issues. The GitHub repository itself is candid about where the project stands — its README opens with a warning that it is “very much R&D” — but it’s a real, actively committed codebase: 92 stars, 16 forks, and 223 commits at the time of writing, with topics tagged creative-coding, processing, and rust.
The $300,000 target, and where the work has already surfaced
The Foundation is raising $300,000 overall for the Development Fund to pay the developers doing this work, and Anthropic’s Titanium-Tier gift is explicitly earmarked toward Processing 5.0’s milestones rather than general operating costs. The clearest public account of the technical approach so far came from Processing Project Lead Moon Davé, whose Libre Graphics Meeting 2026 talk, “Expanding Processing’s Future With a Rust Rendering Engine,” walked through how the team is drawing on the Rust ecosystem — including the Bevy game engine — to bring modern rendering into Processing without starting from scratch. The Rust Foundation’s own “Built with Rust” feature on the project credits Davé and Bevy contributor Charlotte McElwain for the core work, and describes the end goal as a library that can be “dropped into Rust projects, linked into other languages via FFI, or compiled to WebAssembly for browsers” — exactly the one-core, many-faces architecture the Foundation describes.
Why this is the kind of gift that matters here
This site has tracked the Processing Foundation’s funding story before — the $200,000/year Maintenance Fund split between Processing Java and p5.js, announced in October, keeps the existing tools alive. This is different: it’s money aimed at replacing the engine underneath three tools at once with something more maintainable, in a language increasingly trusted for exactly this kind of foundational, safety-critical rewrite. For a community that has watched Processing Java, Python mode, and p5.js drift slowly apart in capability over the years, a single shared Rust core — if it ships — is a structural change with a longer shelf life than almost any single product announcement, which is exactly why it leads today’s round.