The Chrome Experiments site was launched today to feature the JavaScript potential of the new Google Chrome Web browser. A few of the projects, including my contribution called Twitch, use Processing.js. Processing.js is John Resig’s port of the 2D parts of Processing to JavaScript using the Canvas element. I developed my entire project in Processing and then basically cut and pasted it into an HTML file. And there it was, Processing code running inside a browser without a plugin. Twitch was featured at Technology Review today in the post Browser Coders Make Chrome Shine.

Here are a few developing thoughts about Chrome and Twitch:

- Chrome and its fast JavaScript capability offers a glimpse of a Web without proprietary plug-ins. This allows the code (programs) to run directly in the browser rather than loading, for example, the Shockwave Player (from Adobe) or Java (from Sun). This makes it possible to create visually exciting and interesting works without using proprietary tools (in the case of Flash) and works that are accessible to more people (in the case of Java, because many people don’t have the plug-in). This is how innovation on the Web happened back in the mid-1990s; everyone was always looking at how people did things by looking at their HTML code. It made innovation happen quickly. With Flash and Java programs, you don’t have access to the code.

- The piece I created, Twitch, focuses on the genre of one-button games. This is a game that is played with a minimal interface (just one button) and is easy to figure out. I worked to create nine complementary pieces. First, you figure out the controls and then you figure out what to do, without instructions and in a short time. It’s a light piece, meant for enjoyment.

- Technically, I think the greatest innovation of Chrome is launching each Window or Tab as a separate process. If you try to run Twitch on Firefox it starts to slow down as more windows open. Each mini-game competes for the same resources from the computer’s processor. In Chrome, because each window runs separately, the frame rate remains high.

This entry was posted on Wednesday, March 18th, 2009 at 10:58 pm and is filed under Processing.org. You can follow any responses to this entry through the RSS 2.0 feed. Responses are currently closed, but you can trackback from your own site.