Even my husband audibly said "WTF, man????" when he kicked the dog. I didn't hear a peep out of him when the baby was killed though.
*** GoT: House of the Dragon - Season 2***
123,673 Views |
1231 Replies |
Last: 2 mo ago by TyHolden
The Porkchop Express said:The first box is checked, Ser Duncan the Tall looks like a classic Westeros Power ForwardBrian Earl Spilner said:Set a century before #GameOfThrones, the new @HBO Original drama series, A Knight of the Seven Kingdoms, is now in production. Coming soon to @StreamOnMax. pic.twitter.com/CS7tX7iND2
— Game of Thrones (@GameOfThrones) June 18, 2024
He also has a nice wrist watch tan for a knight.
I for one am glad HBO has instituted cruelty to animals in Westeros rather than gratuitous dongs.
A little early in the season to be calling that shot.Al Bula said:
I for one am glad HBO has instituted cruelty to animals in Westeros rather than gratuitous dongs.
Brian Earl Spilner said:
I have zero doubt that moment probably caused the most immediate/visible anger in the bar that films reactions.
"As written..."
Think he'd rather be the Foot of the QueenBrian Earl Spilner said:
So was Larys making a move for himself as Hand?
Well...the King's hand gets to touch the Queen's foot, so
For those who thought the ending didn't work...watch this reaction.
Meh, Jay cries at everything. He cried when C3PO showed up on Ahsoka.Brian Earl Spilner said:
For those who thought the ending didn't work...watch this reaction.
You're not wrong about that.
But, for people who didn't read the book, this is just an example that the tension and dread in that scene was absolutely there, even though it might not have matched what you had in your head from the book.
But, for people who didn't read the book, this is just an example that the tension and dread in that scene was absolutely there, even though it might not have matched what you had in your head from the book.
I didn't read the book and the scene made me hit the pause button ha. It definitely bothered me that they were about to kill a toddler. That being said, I did not think the scene was that well done for many of the reasons stated (prancing through the throne room, they let the mom run off while they killed the boy, there were no guards anywhere to be found, they didn't rip the kids pants off to figure out which was the boy and which was the girl). Also didn't even seem to look for Aemond before settling on the boy.
It's sort of a Catch-22. if it wasn't for the popularity of the books read by millions, there would be no GOT or HOD shows in the first place. Therefore, there are built-in expectations on a lot of things.Brian Earl Spilner said:
You're not wrong about that.
But, for people who didn't read the book, this is just an example that the tension and dread in that scene was absolutely there, even though it might not have matched what you had in your head from the book.
GOT didn't really start veering until season 3 or 4, some of the casting was way off from the books, but that's always going to happen.
Blood was a butcherMonkeyKnifeFighter said:
"Nonsequitur & nonsequitur" more like it.
Cheese was a ratcatcher
I don't see how it would be possible for them to equal the Red Wedding no matter how it was executed. We don't really know this kid...and it's one person vs. hundreds.MonkeyKnifeFighter said:
Now I'm a self-admitted idiot non-book-reader (some may argue that I can't even read) and I caught up last night. That epi ended, and I had zero clue that the end was supposed to be a Red Wedding-level event in the show. Sure I thought that was brutal and is going to have some downstream effects, but the show didn't deliver the same degree of on-screen significance that a lot of other huge GoT milestones do.
Also, "Blood and Cheese"? For a book series/show that does such a great job coming up with catchy nicknames for its milestone events, this one is an F-. It's the names of the 2 assailants, whose names were made up by common folk retelling the story? "Nonsequitur & nonsequitur" more like it. Same zero-inspiration move of just calling a movie the main character's name, leaving it at that, and insisting on source material for significance when the overwhelming majority of the potential audience has zero idea about any of the IP.
Yeah, can agree on this.Quote:
Sure I thought that was brutal and is going to have some downstream effects, but the show didn't deliver the same degree of on-screen significance that a lot of other huge GoT milestones do.
Main reason for this IMO is we spent no time getting to know Aegon's kids, which is understandable given that they're 4 years old.
If they wanted a similar level of impact, they probably should have aged him up, and developed the character more, at least in those last few episodes of S1. But I get why they wouldn't do this, considering how many characters and recasting they were throwing at us already.
If you are not a book reader, do not watch the cast answer the most googled questions video that dropped today.
They insert book spoilers in a pop up at the bottom without any warning.
Got a huge spoiler and immediately closed the video.
They insert book spoilers in a pop up at the bottom without any warning.
Got a huge spoiler and immediately closed the video.
I'm in agreement that...
- It felt out of character for Daemon to hire a couple of doofuses to kill Aemond, instead of instigating a situation where he could ultimately do it himself.
- It was, indeed, kind of ridiculous how little security there was within the castle.
- Yeah, Blood & Cheese would have likely looked for themselves which was the boy and which was the girl. Unless they didn't want to risk waking up the wrong one, the screaming if they woke up the girl, having to keep her quiet while one killed the boy, etc. I can potentially buy that.
That said...
- Wanting that death to be more gruesome or drawn out or whatever seems insane to me. As a non book reader who had no idea what was about to happen, the sounds of knife cutting into flesh were already too much for me.
- I completely disagree with the poster who said that sequence should have been from the POV of Helaena, where the appearance of Blood & Cheese is a surprise. As unbelievable as the lax in security was, personally, I was still absolutely riveted as they made their way through the castle, to the point where getting rid of that sequence seems just as insane as wanting a more gruesome child murder.
- Overall, I found the episode to be the perfect reflection on/button to season one, with multiple surprisingly emotional moments, the best and saddest of which was Jacaerys returning home, his voice cracking as he delivered the news from the North to his mom, and then the two of them embracing. Which then lead to the cutting back-and-forth between the funeral and candle-lighting scenes, which I thought was incredibly well done. I honestly don't understand what else this episode should have been than exactly what it was.
- Throughout the episode, the cinematography/camera movement was incredible, and a step up from even last season. This episode not only looked particularly stunning, but the camera now moves in a way that is so much more assured, focused, and expressive. It's hard to explain, but it was a noticeable and welcomed difference to me.
- It felt out of character for Daemon to hire a couple of doofuses to kill Aemond, instead of instigating a situation where he could ultimately do it himself.
- It was, indeed, kind of ridiculous how little security there was within the castle.
- Yeah, Blood & Cheese would have likely looked for themselves which was the boy and which was the girl. Unless they didn't want to risk waking up the wrong one, the screaming if they woke up the girl, having to keep her quiet while one killed the boy, etc. I can potentially buy that.
That said...
- Wanting that death to be more gruesome or drawn out or whatever seems insane to me. As a non book reader who had no idea what was about to happen, the sounds of knife cutting into flesh were already too much for me.
- I completely disagree with the poster who said that sequence should have been from the POV of Helaena, where the appearance of Blood & Cheese is a surprise. As unbelievable as the lax in security was, personally, I was still absolutely riveted as they made their way through the castle, to the point where getting rid of that sequence seems just as insane as wanting a more gruesome child murder.
- Overall, I found the episode to be the perfect reflection on/button to season one, with multiple surprisingly emotional moments, the best and saddest of which was Jacaerys returning home, his voice cracking as he delivered the news from the North to his mom, and then the two of them embracing. Which then lead to the cutting back-and-forth between the funeral and candle-lighting scenes, which I thought was incredibly well done. I honestly don't understand what else this episode should have been than exactly what it was.
- Throughout the episode, the cinematography/camera movement was incredible, and a step up from even last season. This episode not only looked particularly stunning, but the camera now moves in a way that is so much more assured, focused, and expressive. It's hard to explain, but it was a noticeable and welcomed difference to me.
The shot that goes across the table to Rhaenyra's face was fantastic.
So, so good.
Yep. We spend 3 seasons with Robb, Catelyn, lots of scenes of Talisa being this kind-hearted idealist queen, Arya has been on the run for two season and is about to reunite with her family and then it all gets flushed down the drain in 15 minutes.Diggity said:I don't see how it would be possible for them to equal the Red Wedding no matter how it was executed. We don't really know this kid...and it's one person vs. hundreds.MonkeyKnifeFighter said:
Now I'm a self-admitted idiot non-book-reader (some may argue that I can't even read) and I caught up last night. That epi ended, and I had zero clue that the end was supposed to be a Red Wedding-level event in the show. Sure I thought that was brutal and is going to have some downstream effects, but the show didn't deliver the same degree of on-screen significance that a lot of other huge GoT milestones do.
Also, "Blood and Cheese"? For a book series/show that does such a great job coming up with catchy nicknames for its milestone events, this one is an F-. It's the names of the 2 assailants, whose names were made up by common folk retelling the story? "Nonsequitur & nonsequitur" more like it. Same zero-inspiration move of just calling a movie the main character's name, leaving it at that, and insisting on source material for significance when the overwhelming majority of the potential audience has zero idea about any of the IP.
We spend 2 minutes with Aegon's son lol
Put me in the camp as not realizing the full impact killing the little boy would have. Had no idea until reading on here that it was basically the match that lights the entire thing up. I was just confused why they were going for the little boy instead of Aemond. (Or whatever his name is....the one-eyed guy. I can't keep the names straight.)
AJ02 said:
Put me in the camp as not realizing the full impact killing the little boy would have. Had no idea until reading on here that it was basically the match that lights the entire thing up. I was just confused why they were going for the little boy instead of Aemond. (Or whatever his name is....the one-eyed guy. I can't keep the names straight.)
I don't get this at all, though.
The match had already been lit in Aemond killing Lucerys. And then Otto's whole deal this episode is that war is inevitable. So killing the kid at the end of this episode didn't start anything, didn't lead to war, etc. All of that was already so far in motion. All it did was now make it personal for the Hightowers.
So even in the books I don't understand how this was supposed to be some monumental, game-changing event, nor did I get the impression that the show was trying to make it one either. Rather, the match had already been lit, and the two sides were already on a collision course, except now it's personal for both of them.
As for why they were going after the little boy, it's "explained" in the previous scene when Blood & Cheese ask what they should do if they can't find Aemond. It cuts away before Daemon answers, but he presumably told them to then kill the four-year-old son instead.
Totally agree. Alicent was still holding out hope (albeit false hope) that maybe this could be resolved peacefully. Otto knew that wasn't possible and said as much. War was inevitable, but Alicent didn't really want it. But now after they killed her grandson you better believe she is all the way in and going to say "**** it - let's tear them apart". (I assume - I'm not a book reader)TCTTS said:
The match had already been lit in Aemond killing Lucerys. And then Otto's whole deal this episode is that war is inevitable. So killing the kid at the end of this episode didn't start anything, didn't lead to war, etc. All of that was already so far in motion. All it did was now make it personal for the Hightowers.
Exactly.
Prior to Blood & Cheese, Targareyns had only died from old age, the rare childbirth mishap, or in direct combat. They perpetuated the myth throughout the seven kingdoms that they couldn't be killed, and that they were resistant to fire (a few were, like Dany).TCTTS said:
So even in the books I don't understand how this was supposed to be some monumental, game-changing event, nor did I get the impression that the show was trying to make it one either. Rather, the match had already been lit, and the two sides were already on a collision course, except now it's personal for both of them.
The fact that 2 young punks got into a fight on dragons and one killed the other would be the equivalent of the US and China winding up with fighter jets in the same airspace and an American pilot gets killed by an errant missle. Yes, the WHOPR computer probably drops to Defcon 2 or 4, or whatever way it goes, but you'd still want to assume the two superpowers could negotatie a truce.
But if the US responded by hiring some black ops Thai death squad to go to the Chinese Premiere's house and murder his grand son, well now, now we're talking World War III.
It's the triple whammy of killing the heir, killing a kid, and having a couple of common thugs do it, because if that gets out, then everyone starts thinking, hell the Targs are mortal, they can be killed, once those Dragon numbers start getting pared down, what's to stop the rest of us from getting out from under their thumb? Which is of course what eventually happens once they struggle to hatch more dragons that grow to full size, and then hatch dragons at al.
Luke wasn't a random pilot though?
The Porkchop Express said:Prior to Blood & Cheese, Targareyns had only died from old age, the rare childbirth mishap, or in direct combat. They perpetuated the myth throughout the seven kingdoms that they couldn't be killed, and that they were resistant to fire (a few were, like Dany).TCTTS said:
So even in the books I don't understand how this was supposed to be some monumental, game-changing event, nor did I get the impression that the show was trying to make it one either. Rather, the match had already been lit, and the two sides were already on a collision course, except now it's personal for both of them.
The fact that 2 young punks got into a fight on dragons and one killed the other would be the equivalent of the US and China winding up with fighter jets in the same airspace and an American pilot gets killed by an errant missle. Yes, the WHOPR computer probably drops to Defcon 2 or 4, or whatever way it goes, but you'd still want to assume the two superpowers could negotatie a truce.
But if the US responded by hiring some black ops Thai death squad to go to the Chinese Premiere's house and murder his grand son, well now, now we're talking World War III.
It's the triple whammy of killing the heir, killing a kid, and having a couple of common thugs do it, because if that gets out, then everyone starts thinking, hell the Targs are mortal, they can be killed, once those Dragon numbers start getting pared down, what's to stop the rest of us from getting out from under their thumb? Which is of course what eventually happens once they struggle to hatch more dragons that grow to full size, and then hatch dragons at al.
I hear what you're saying overall, and I appreciate the context, but the show itself directly contradicts the bolded text above. Again, at this point there was no talk of negotiations. War was inevitable, and Alicent was the last holdout, then end of this episode changed that. Never mind the fact that it wasn't "errant." Aemond directly attacked Lucerys. Sure, he wasn't trying to kill him, but he was absolutely trying to harm him.
A ******* is as random as you get.Brian Earl Spilner said:
Luke wasn't a random pilot though?
Damn you TxAgs and your dick rules about the words I can say and can't say. Basterd. Bastarrrrd, what does it take?
I'm not sure anyone asked for a more gruesome child murder, just a more impactful murder scene. I was left feeling nonplussed because they made no attempt to endear these children to the audience. There's several memes discussing how more people were upset about the dog getting kicked rather than a child being murdered and that's because they did a poor job of having us care about the children.
No material on this site is intended to be a substitute for professional medical advice, diagnosis or treatment. See full Medical Disclaimer.
Fun fact, nonplussed actually means the opposite of that.
Meh, the more common utilization nowadays is "unfazed", so much so that it is a recognized definition of the word.
No material on this site is intended to be a substitute for professional medical advice, diagnosis or treatment. See full Medical Disclaimer.
It is unfair to call Luke a "random pilot." He did spend his formative years running the salt flats of Tatooine wasting time with his friends under the premise of obtaining power converters from Tosche Station, however his family history of Force-sensitivity and latent laser sharp fightercraft abilities prove appearances can be deceiving.Brian Earl Spilner said:
Luke wasn't a random pilot though?
Featured Stories
See All
23:41
7h ago
1.3k
Two-game slide ends as No. 11 Texas A&M tames LSU at Reed, 68-57
by Olin Buchanan
4:53
7h ago
457
Game Highlights: No. 11 Texas A&M 68, Louisiana State 57
by Matthew Dawson
Photo Gallery: No. 11 Texas A&M 68, Louisiana State 57
by Will Huffman
75:17
1d ago
8.0k
Backyard Gator
Create something out of nothing: Sark contract extension
in Billy Liucci's TexAgs Premium
13