3 ms·

I don't think so; the passage of 'time' measured in the simulation could be quite a bit faster/slower than on the hardware underlying the simulation (I would as

I don't think so; the passage of 'time' measured in the simulation could be quite a bit faster/slower than on the hardware underlying the simulation (I would assume quite a bit 'slower'). So if we were in a simulation, I'm skeptical that we could guess much about the properties of the 'host' system.

ak39 10y ago
But we can determine the maximum speed of causality, can't we? I was watching a (Bostrom, I think ?) presentation where the vocabulary used to explain Einstein's "c" (the speed of light) included words like "maximum speed of causality". That blew my mind. Because light moves as fast as it theoretically can (many Newtonians believed there was no ubound to the speed of light), light speed still cannot breach the absolute limit of 299 792 458 m/s. That speed limit is embedded directly into the action-reaction architecture of our universe. (Anyway, didn't mean to hijack)
- joshmarlow 10y ago
  That's a super interesting point actually. I'd never thought of the "maxium speed of causality". Thanks for sharing! We could determine the maximum speed within our terms, but again that doesn't necessarily translate to how things happen in the underlying substrate. Thought experiment: let's imagine we create our own simulated environment and put a sentient AI into it (which is implemented in the physics of that environment). The AI gets curious and does some experiments and figures out the maximum speed that causality can propagate in it's environment. Suppose the speed of light in the simulation is as fast as the speed of light in our environment. So something takes 1 in the simulation and 1 second in ours. Cool. Now, suppose you and I as the developers put in a 'sleep' call into the event loop or whatever so that the simulation runs at 1/10 the speed of real time. Light in the simulation is now 10 times slower than it was by our clock time. Now the code operates considerably slower - but any entity in the code wouldn't perceive the slowdown because it has slowed down too in the same way. Same thing - any slowdown in the simulation would not be noticeable to us because it's also a slowdown in us.

ak39 10y ago

But we can determine the maximum speed of causality, can't we? I was watching a (Bostrom, I think ?) presentation where the vocabulary used to explain Einstein's "c" (the speed of light) included words like "maximum speed of causality". That blew my mind. Because light moves as fast as it theoretically can (many Newtonians believed there was no ubound to the speed of light), light speed still cannot breach the absolute limit of 299 792 458 m/s. That speed limit is embedded directly into the action-reaction architecture of our universe. (Anyway, didn't mean to hijack)

joshmarlow 10y ago
That's a super interesting point actually. I'd never thought of the "maxium speed of causality". Thanks for sharing! We could determine the maximum speed within our terms, but again that doesn't necessarily translate to how things happen in the underlying substrate. Thought experiment: let's imagine we create our own simulated environment and put a sentient AI into it (which is implemented in the physics of that environment). The AI gets curious and does some experiments and figures out the maximum speed that causality can propagate in it's environment. Suppose the speed of light in the simulation is as fast as the speed of light in our environment. So something takes 1 in the simulation and 1 second in ours. Cool. Now, suppose you and I as the developers put in a 'sleep' call into the event loop or whatever so that the simulation runs at 1/10 the speed of real time. Light in the simulation is now 10 times slower than it was by our clock time. Now the code operates considerably slower - but any entity in the code wouldn't perceive the slowdown because it has slowed down too in the same way. Same thing - any slowdown in the simulation would not be noticeable to us because it's also a slowdown in us.