Processing: Revolutionary Creative Coding Tool Now 1.0, No Longer Beta
The creative, visual development platform Processing has undergone what may be one of the longest, strangest betas ever – in a good way. What other “beta” has had tomes written about it, tens of thousands of students studying it (in some large programs, as the basis of their work), rockstar music videos made with it, museum exhibitions, major ads, print graphics, motion graphics – all over the course of a number of years.
Download Processing, and you might be forgiven for thinking this “beta” thing would last forever. Insanely frequent updates only reinforce that idea, as though “beta” really meant “ongoing development.” And after all, the software isn’t like other apps. It’s entirely open source and free. First download it, and you’re presented with what seems like a stripped-down text editor. There’s no real manual, as such: instead, you delve into an elegantly-composed reference to commands, and the real “help” is in the form of folders of example code. Yet this environment is capable of visualizing data, crunching 2D and 3D imagery, video, sound, and via external libraries, anything that you can do with Java – opening it to one of the most-extended platforms around.
But believe it: the beta really has ended. As of Monday, Processing the “beta” is now just Processing. The number scheme has changed, too: it’s just 1.0 now (0162, if you’re still counting, though it will no longer officially be called that).
We’re really pleased on this site that Processing has hit 1.0, not just because of what this tool itself means, but because of the bright future we see for expressive visuals, live visual performance and visual interaction, and the DIY creative movement. Over the coming days and weeks, we’ll have everything from learning materials to interviews to celebrate the launch. Someone somewhere ought to really get some champagne (or considering it’s based on Java, maybe some Irish Coffee). And after years of waiting, coding, learning, artmaking, and an epic development effort by co-creators Ben Fry and Casey Reas, the core developer team, and the wider community, I think this deserves more than just a few hours of attention. Given what Processing has done in beta, it’s almost (wonderfully) terrifying to think what it could do after 1.0.
What’s changed, current users?
If you’re a current user, you’ll want to take a real look at the change log, because the last few weeks of coding have brought more rapid change and bug stomping than any time in recent Processing history. Some highlights:







