The processing.js project was started by John Resig who wanted to utilize the HTML5 canvas element and take advantage of the Java Processing language. It took about seven months to get a working version, consisting of 5000 lines of code but it was not a complete port of the Processing language. The project, similarly to other open source products, was released with the hope that a developer community will converge around it and contribute to development. In September 2009, we began the work to complete the port to JavaScript. In order to facilitate an architecture for participation the source code had to be readily available and the inner workings of the project and the missing functionality must be publicized. To this end the source code was made available publicly on GitHub and an issue tracking system was used to manage the large number of issues needed to be resolved in order to complete the port. A review process was setup to ensure that the code submitted was of sufficient quality.

"The Mozilla experience howeverFrom it's inception, suggests that proprietary products may not Processing.js was designed to be well-suited to distributed development if they have tightly-coupled architectures. There is more than just a need to create an “architecture for participation,” one that promotes ease rewrite of understanding the Java functions provided by limiting module size, and ease of contribution " - (MacCormack, Rusnak and Baldwin 2004)Processing to JavaScript. In September 2009, we began John Resig wrote the work to complete the port to JavaScriptoriginal Processing. In order js parser to facilitate an architecture scan a Processing sketch for participation a number hints of things needed to happen. First Java code and foremost the source convert that code had to be readily availableJavaScript. Secondly However, if the inner workings of parser encountered JavaScript code, it would leave the project and the missing functionality must be publicized and a dialog startedcode intact. To this end This method allowed not only for the source conversion of existing Processing code was made available publicly on GitHub and an issue tracking system was used to manage JavaScript but the large number injection of issues needed JavaScript into Processing sketches as well. By allowing JavaScript to be resolved in order exist within a Processing Sketch intact,Java and JavaScript code can exist together without any need to complete declare the portlanguage you are using. A review process was setup Old sketches written for Processing will work but new sketches written for Processing.js can not only have Processing code but can make use of JavaScript to ensure that interact with other elements of the code submitted was of sufficient qualitywebpage.