When this movie first came out, a certain group of fans were obsessed with it (myself included). We'd watch it over and over, attempting to figure out the different timelines, how much of the science had been done (2004), and how much was never explicit/explained, nor what the time loops/branches were or could be. However, any movie name dropping Feynman probably has reasonable science, at least in theory.
Several people actually created flowcharts to show how the movie was written and the loops were constructed; not all flowcharts corresponded back in the original debates.
The initial and ending "tape/overdubbing" by Aaron as well as the jump cut to Abe being passed out and awoken by Aaron early on gives away (eventually) that Aaron eventually becomes the controlling character - though in the movie he is a close friend/co-inventor with Abe up to a crucial point. I think overdubbing what's in a character's mind is a useful film device, though I'm aware many people have differing views on that in film. Here, with the complexity, it helps to give the watcher some grounding in a challenging storyline. The film is very complex the first time you watch it.
Aaron and Abe's characters are the only ones really fleshed out in the script. All the other characters, including Aaron's wife, Abe's girlfriend, and her father (the potential VC for Aaron, Abe, and two other ambitious engineers involved early in the movie) are plot devices more than actual characters.
This makes the rest of the film more of a 2D backdrop, which is why I didn't give it a 10. Shane Carruth did an incredible job writing, producing, directing and starring in this movie - except for his supporting character development.
If you are a science fiction/time travel film lover, and/or an engineering, computer science, or any applied math-based professional, the content and upfront presentation of the film can easily draw you in. The film's beginning engineering & development cycle, mention of VC, and flowcharts of the logic behind the film afterwards I mentioned earlier are comparable to systems development for any type of public/private/academic applied math project (engineering, computer science, physics, etc.).
It takes only one viewing of this movie to be fascinated with it. You might wind up watching it more than that - say, at least a couple of times a year.
Several people actually created flowcharts to show how the movie was written and the loops were constructed; not all flowcharts corresponded back in the original debates.
The initial and ending "tape/overdubbing" by Aaron as well as the jump cut to Abe being passed out and awoken by Aaron early on gives away (eventually) that Aaron eventually becomes the controlling character - though in the movie he is a close friend/co-inventor with Abe up to a crucial point. I think overdubbing what's in a character's mind is a useful film device, though I'm aware many people have differing views on that in film. Here, with the complexity, it helps to give the watcher some grounding in a challenging storyline. The film is very complex the first time you watch it.
Aaron and Abe's characters are the only ones really fleshed out in the script. All the other characters, including Aaron's wife, Abe's girlfriend, and her father (the potential VC for Aaron, Abe, and two other ambitious engineers involved early in the movie) are plot devices more than actual characters.
This makes the rest of the film more of a 2D backdrop, which is why I didn't give it a 10. Shane Carruth did an incredible job writing, producing, directing and starring in this movie - except for his supporting character development.
If you are a science fiction/time travel film lover, and/or an engineering, computer science, or any applied math-based professional, the content and upfront presentation of the film can easily draw you in. The film's beginning engineering & development cycle, mention of VC, and flowcharts of the logic behind the film afterwards I mentioned earlier are comparable to systems development for any type of public/private/academic applied math project (engineering, computer science, physics, etc.).
It takes only one viewing of this movie to be fascinated with it. You might wind up watching it more than that - say, at least a couple of times a year.
Tell Your Friends