zlacker

[parent] [thread] 4 comments
1. sudhir+(OP)[view] [source] 2020-03-17 08:33:24
Not to rewind. Rewind implies changing something in your own past, but nobody's past changed. Only the futures of different timelines, if that makes sense.
replies(3): >>mav3ri+5e >>MertsA+4v >>mixmas+VV
2. mav3ri+5e[view] [source] 2020-03-17 11:24:42
>>sudhir+(OP)
A good way to think of this is a git checkout from anywhere . And then all future commits happen in a branch / detached head state, not affecting the place you checked out from i.e. original timeline.
replies(1): >>jimmyd+Vr1
3. MertsA+4v[view] [source] 2020-03-17 13:50:28
>>sudhir+(OP)
That was exactly how it was used in Doctor Strange. It's just a movie, they play fast and loose with the rules all the time.
4. mixmas+VV[view] [source] 2020-03-17 16:19:33
>>sudhir+(OP)
They made a big deal about that for a movie, considering it is all fantasy. It’s a distinction without practical meaning for storytelling purposes. Just to avoid the scene where Marty sees his own foto fade. They could have just ignored it.
◧◩
5. jimmyd+Vr1[view] [source] [discussion] 2020-03-17 18:38:19
>>mav3ri+5e
They made a big deal out of it in the movie, that the stones had to be returned to the exact time they were taken from, or else they would be changing the future of the old "head".
[go to top]