tom moody

tom moody's weblog
(2001 - 2007) (2004 - )

2001-2007 archive

main site


digital media tree (or "home" below)

RSS / validator

BLOG in gallery / AFC / artCal / furtherfield on BLOG

room sized animated GIFs / pics

geeks in the gallery / 2 / 3

fuzzy logic

and/or gallery / pics / 2

rhizome interview / illustrated

ny arts interview / illustrated

visit my cubicle

blogging & the arts panel

my dorkbot talk / notes

infinite fill show




coalition casualties

civilian casualties

iraq today / older

mccain defends bush's iraq strategy

eyebeam reBlog


tyndall report

aron namenwirth

bloggy / artCal

james wagner

what really happened


cory arcangel / at

juan cole

a a attanasio

three rivers online

unknown news



edward b. rackley

travelers diagram at

atomic cinema


cpb::softinfo :: blog


paper rad / info

nastynets now

the memory hole

de palma a la mod

aaron in japan


chris ashley




9/11 timeline

tedg on film

art is for the people


jim woodring

stephen hendee

steve gilliard

mellon writes again


adrien75 / 757


WFMU's Beware of the Blog

travis hallenbeck

paul slocum

guthrie lonergan / at

tom moody

View current page
...more recent posts

Artist and blogger twhid responds here to the previous posts (1 / 2) on whether it's necessary to know code to make digital art:
I find myself on both sides of this issue.

On one hand, I donít think itís necessary to be able to program a computer to make digital art.* Especially as the tools to create digital art get better and better. And besides, what is the difference between Windows APIs and the the interface of Photoshop? They both present you with tools to make things happen on a computer.

On the other, I think having programming knowledge is very important (but not necessary) for one to be a digital artist. I would argue that instead of Tomís analogy of a painter grinding his own paint, a better analogy is that a painter must understand how color and 2d form work. For those are the building blocks of a painting really, not the paint. Itís a mistake to confuse a computer for a canvas, to think of it simply as a means to a visual end. A computer does much more than display images on its display. With much new media art the how of image creation is just as important as the images themselves.

*Of course you get into a whole other argument if you do agree: is writing in a scripting language programming? How low-level is the code you program? Is programming in C++ somehow Ďbetterí than programming in Java? etc, etc.
I had hoped to make it clear that the canvas analogy isn't good, since there are decades of theory showing the canvas is a far from neutral surface and the rectangle an inherited convention that can be subverted: much modern art is about dismantling the tools of painting, conceptually, not just physically. Arguably new media art built on this existing conceptual framework of modern and poMo theory--applying its precepts to the computer, video, etc.

My "grinding paint" analogy was chosen precisely because it invokes the nerdy, irrelevant side of art. It's a Renaissance technology (and accompanying set of problems) that some painters unbelievably still find vital in the modern/poMo era. If knowing how to program results in some extreme refinement that Photoshop couldn't give you but is not visible to any reasonably sized art audience, then who cares about it? Those were the thoughts I had on seeing John Maeda's shows: so he can program? That means he can make more finely adjusted screen savers.

- tom moody 10-14-2004 7:42 pm [link] [5 comments]