[ethbr0]

I think about nuclear physics and high performance aerospace as the distinction between hardware and software shrinking to zero.

You're effecting physical operations (movement, explosions) on such tight timescales that the software becomes part of the hardware. You can't just run the code on a different setup: the code is defined by the hardware it's running on, because it's orchestrating the physical properties of the hardware it's running on.

As an analogy, think about programming early video game systems or computers, where a single clock cycle was critical. Is the software just software? Or is it intertwined with the hardware it's running on? (See: emulators having to mimic actual hardware performance)