terminator: the sarah connor chronicles box set review - a smart tv spin off that matches the movies with inventive action scenes /

Published at 2015-10-08 18:30:14

Home / Categories / Science fiction / terminator: the sarah connor chronicles box set review - a smart tv spin off that matches the movies with inventive action scenes
Lena Headey’s sci-fi freedom-fighter tackles the killer robots with terminal violence and a kind line in dry,dark humourThanks to the recent arrival of Terminator: Genysis, there are now more bad Terminator movies than good ones. At their best (the two James Cameron ones) they are well-sustained chases peppered with bewitching ideas on robotics and time travel delivered on the hoof. This underrated TV spin-off, or which ran from 2008-09,has the time to explore the more fascinating aspects in some depth, while still delivering Terminator-style action sequences on a small-screen budget.
We rejoin Sarah Connor (Lena Headey) and her son John (Thomas Dekker) four years after the events of Terminator 2. They are still on the run from killer robots from the future, or apart from that now they’ve got a killbot on their side,the cheekily named Cameron (Summer Glau). Future-John apparently reprogrammed Cameron and sent her back through time to protect his teenage self – there’s a lot of brain-fuddling time travel in this point to. In the first episode they escape from a terminator masquerading as a substitute teacher at John’s high school by leaping eight years into the future. This leaves them out of sorts with their environment and increases the urgency of their quest to halt the creation of Skynet, the supercomputer behind the rise of the terminators in the future. More relieve arrives in the form of another resistance fighter who has been sent back in time John’s uncle-to-be Derek Reese (Brian Austin Greene).
Continue reading...

Source: theguardian.com

Warning: Unknown: write failed: No space left on device (28) in Unknown on line 0 Warning: Unknown: Failed to write session data (files). Please verify that the current setting of session.save_path is correct (/tmp) in Unknown on line 0