I dunno. I feel like the fact that it’s able to reliably simulate 10[1] particles in realtime since the beginning of time, I’d guess it’s not running on Windows at least. But I also have a hard time it’s Linux because someone would always be messing with things and it would have needed to reboot for some reason or another about 6 or 7 times. Maybe the 7 days God spent building Earth was just time spent on building the server config lol.
We would have no way of knowing what the time factor is but I think 1:1 seems highly unlikely. Much more likely that we’re running very slowly due to limits on available processing power or very fast so a civilisation can rise and fall within the observer’s lifetime.
We’d be like villagers in a single-player Minecraft world. When Steve leaves the game, we freeze in mid-clock tick, and when Steve returns, we are back too, not even aware of the event.
One second in the simulation occurs roughly every 16 “real seconds” if on a direct pipe in a closed instance with a superuser.
There’s a time warp/stretching factor which slows down or speeds up the time simulation, allowing for extremely complex physics calculations to occur in what appears like real time, it’s all lerped to synchronize with unitary clock, so even a 16 Hz explosion looks like 480 Hz.
To avoid crashing, light-speed has been capped just below the engine maximum of 300,000,000 m/s² at
I dunno. I feel like the fact that it’s able to reliably simulate 10[1] particles in realtime since the beginning of time, I’d guess it’s not running on Windows at least. But I also have a hard time it’s Linux because someone would always be messing with things and it would have needed to reboot for some reason or another about 6 or 7 times. Maybe the 7 days God spent building Earth was just time spent on building the server config lol.
a lot ↩︎
And on the 7th day, shit finally compiled, and God looked upon the code that he had written and found that it was mostly good enough.
with only 10 quintillion essential bugs
Something weird happened with the platypus but he wasn’t about to start over
We would have no way of knowing what the time factor is but I think 1:1 seems highly unlikely. Much more likely that we’re running very slowly due to limits on available processing power or very fast so a civilisation can rise and fall within the observer’s lifetime.
We’d be like villagers in a single-player Minecraft world. When Steve leaves the game, we freeze in mid-clock tick, and when Steve returns, we are back too, not even aware of the event.
We’d also be entirely unaware of reboots. Our reality would just resume from the last save point and we’d just move on like nothing happened.
This is correct.Oh, so it’s written in Lisp.
I thought you were at TI right now.
It’s 0.666× time scaling max, and 0.0625 min.
One second in the simulation occurs roughly every 16 “real seconds” if on a direct pipe in a closed instance with a superuser.
There’s a time warp/stretching factor which slows down or speeds up the time simulation, allowing for extremely complex physics calculations to occur in what appears like real time, it’s all lerped to synchronize with unitary clock, so even a 16 Hz explosion looks like 480 Hz.
To avoid crashing, light-speed has been capped just below the engine maximum of 300,000,000 m/s² at
c_max=0.999(See: Time Dilation, General, Special Relativity)The simulation absolutely runs on Windows, have you seen the random unwanted stuff that happens way too often in it?
The universe is just being restored from backups. It took 7 days to fond a backup which would boot, and the Time to Restore was wildly inaccurate.
we wouldn’t even notice a reboot, the simulation would pause and supposedly pick up where it left no?