>Things in superpositions only becoming "set" after observation... that is just lazy evaluation.
I've always thought about it this way also, I'd love to get a source on where you read it so I can see a different take than my own.
Some other things to consider:
1. Planck length is the most granular unit or pixel the computer can measure.
2. The time it takes to move one Planck length at the speed of light is the time of one iteration of the simulation's "main loop".
3. The reason time dilates as you approach the speed of light is because the faster a particle moves, the more the main loop must access that particle, and the more the particle's state may be in a "being processed" lock where it can't be mutated by anything else.
Just some thing I've always thought about when trying to see if I could use code patterns and processes to quantify the behavior of the universe. Of course, I wouldn't say I believe these things as fact or anything, just awesome to think about.
There's a simpler reason, I think. Any mechanism or "clock" must have moving parts of sorts (atoms, exchange particles like photons, etc.) which means that when functioning or "ticking", some parts move faster than some other parts. But if the mechanism is moving at the maximum speed, it can only be the case that some parts move at c, and others move slower, but these slower parts can never catch up, so the clock disintegrates. It can only remain whole if all parts move at maximum speed, which means it is static: it is frozen in time.
I imagine that given a speed distribution for all components of the mechanism, there would be a smooth time dilation effect as the speed of the whole mechanism increases. I'd have to calculate. In any case, I think time dilation is basically necessary in a system with a maximum speed. I'd expect to see something similar in cellular automata, regarding complex objects that can move at various speeds.
> Isolating each "light cone" of local spacetime allows the simulation to be distributed and run on separate compute clusters, because it limits things to local interactions rather than universal ones.
I don't know if that would make a difference. If you split the universe into zones and assign a cluster to each, they still have to interact with each other all the time because of the boundary. Besides, in a universe where interactions can be "universal", what's the performance gain of local algorithms?
> Things in superpositions only becoming "set" after observation... that is just lazy evaluation.
Really, though, what collapses a quantum state is interaction in general. It happens everywhere, all the time, so I don't know if there's actually anything to gain with this "lazy" evaluation.
Lazy evaluation is generally used to defer some expensive computation until later. In this case, though, the pre-measurement state (a superposition of states) is MORE complicated (computationally speaking) than the post-measurement state, which is nominally a single definite state. It's not a good analogy I'm afraid.
When this function is called, it causes some algorithm to set up these data points. You can extend this to treat entanglement as copy-on-write style branching, where entangled particles A and B have some subset of their properties stored in the same physical memory, but calling this methods causes writing to those properties, and, thus, when the function is called for particle A, a copy of the properties is made for both A and B, and the evaluation is done for both.
IMO the biggest reason to think the universe isn't a computer is just how darn non-computable quantum mechanics is. The complexity grows at an absurd rate. Even for just the position of two particles you have a 6-dimensional wavefunction with (as far as we know) an infinity of possible values for every (infinitesimal) point in that 6-dimensional state space.
If an intelligence is simulating a universe, they aren't exactly going to be doing it von-neumann style.
I remember reading once that the limitation on speed of light could be a performance optimisation. Isolating each "light cone" of local spacetime allows the simulation to be distributed and run on separate compute clusters, because it limits things to local interactions rather than universal ones.
Things in superpositions only becoming "set" after observation... that is just lazy evaluation. It's fun to think about.