[javajosh]

Indeed, and it's fun to look at the remarkable differences, which are usually more visible in these early stages of development. It gets to the very heart of what "state" is; the beginning of computation really goes back further, to automata and Charles Babbage, where state is encoded into the position of a cog, and decoded by looking at the cog.

For quantum computing, state is written into the wave function of an isolated particle, which is entangled with other isolated particles such that you can perform a read and get something useful out of it. (TBH I'm a little confused about how QC works at the physical level, because it seems like your program could require different patterns of entanglement, but AFAIK the pattern of qubit entanglement is determined by the hardware setup, and cannot be modified at runtime. Maybe there is a generally reusable "shape" that can be interacted with, cleared, setup for a new computation, etc by poking at the particles in some specific order. It's probably a really nice problem for physics folks who feared they'd never get to use their QM classes.)