Friday 19 April 2013

The Big Moff and 'Who''s Golden Rules

 I'm not sure what Sydney Newman (you know, the guy who basically invented 'Doctor Who') would think of the title of season 7's finale episode. Being dead there don't seem to be  many options left but turning over in his grave, even though, he may wait and save that for another occasion, like when someone will turn the Doctor into a woman (*shudder*). But teasing to reveal the biggest mystery in the Whoniverse comes actually pretty close to that. Well, we know Moffat is not *really* up to it. After all, this series is called 'Doctor Who' for a reason,and I'm pretty sure Moffat is aware of that too.You simply cannot go and break 'Who's golden rules at your will.

Sadly, it's almost as if Moffat's big goal was to try how far he can go interfering with those aforementioned rules without actually breaking them: he made the Doctor marrying River, he even killed him, and know he's trying to reveal the one secret which nobody really wants to know. Well, we know it's much ado about nothing, as Moffat has a record on not keeping his promises, but even teasing things like this should be forbidden. If you add something to that part of 'Who's legacy then it becomes to stay forever, just like that odd 13-lives rule (which is there for a really important reason, so I'm not complaining). And as much as I love most of Moffat's episodes, I'm not sure if I want him to have this much power. Because if you're messing with the Doctor's past you're craving your own ideas into stone, and future main editors will have to stick to them, no matter if they like it or not, or if it's worth it. 

On the other side, this is something which would have happened at one point in the future anyway. And I can come up with much worse scriptwriters than Moffat who could have had a go at it (I'm glad RTD didn't). So we can deal with it know, and settle things forever. And let's hope that Moffat has a brilliant solution to deal with this very obvious red herring, i.e. without causing too much damage.

No comments:

Post a Comment