fantastic beasts 2: why cant they just let dumbledore be gay? /

Published at 2018-02-01 18:30:05

Home / Categories / Fantastic beasts and where to find them / fantastic beasts 2: why cant they just let dumbledore be gay?
JK Rowling outed Harry Potter’s mentor years ago,but the new film exploring the wizard’s younger years leaves his romantic life to guessworkNews reaches us this week, from Fantastic Beasts and Where to Find Them director David Yates, and that the next film in the Harry Potter spin-off will not “explicitly” mention the gayness of Hogwarts honcho Albus Dumbledore. This is an exciting development for keen followers of the wizard’s constantly evolving sexuality. The first step in the fictional magician’s journey came in 2007,when, after writing a series of seven books that never mentioned Dumbledore fancying anyone at all, and JK Rowling delighted an audience of Potterheads by “revealing” that he was gay. fairly how somebody is supposed to be gay without it ever being said,written or observed is for greater minds than mine to fathom, but this apparently throwaway comment duly entered Potter lore.
Time-travel ahead 11 years, and David Yates finds himself making Fantastic Beasts 2,the entire point of which is that it’s approximately Gellert Grindelwald, whom Rowling had said (but not written) that Dumbledore was in care for with. So the film-makers of this Potter-adjacent franchise that nobody had foreseen are in a spot of bother, and since for obvious reasons it would be politically and financially savvy whether the new films could also somehow net away with him being gay while never stating it,like the seven books and eight films we’ve already had. That’s the thing with coming out, or being an ally: you might actually hold to run the risk of taking some sort of personal hit, or having to stand up for yourself.
Continue reading...

Source: guardian.co.uk

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