While relegation maybe more dramatic it would have been irrelevant this year based on the current table, so top 8 and top 4 drama is all we would have anyway.
8 and only 8.The question is where would you play Tom?
That's why I said current table. You are right though, it could well have been different without the pressure.Hard to say it's irrelevant since you don't know how teams would've faired with that pressure on their backs.
I can totally understand why you're hacked off but 'Bloodgate' was in a major European game. Relatively speaking the result of this game isn't important enough or high profile enough to cause that type of furore.Will take me a while to get over Lam, Bristol and the officials today.
Hopefully this blows up like 'Bloodgate' did but I personally can't see it. In the eyes of Prem Rugby and BT, Free-flowing Bristol can do no wrong! The current darlings of English rugby (god knows why) will avoid punishment and this will be brushed under the carpet.
Oh and to top it off Irish get two more points with Wasps getting 5.
28% win rate and in with a huge chance of Champions Cup rugby
John Afoa got injured a couple of weeks ago at the Gloucester game and was due back next week.
On Thursday Kyle felt his hamstring tighten up and he failed a fitness test. We made a call to start John and then bring him off at half-time.
At the end we had the yellow card. I thought John had come off as an injury [replacement], but it was down as tactical.
No but threatening the ref might be. Lam said something along the lines of "If he goes back on and gets injured, it's on you" to the referee. That's pretty much a threat and needs addressing. If Lam felt that strongly about Afoa's safety than surely he'd have stood his ground, but no..... The fault in this situation is 100% with Bristol and no one else. Lam's post-hoc rationalisation (player safety) was quite clever but utter horseshit. It was only when it dawned on Bristol that they'd be playing with 13 rather than 14 that Lazarus Afoa decided he was in fact fine to return to the fray. Which was funny because resting an old fella because he's a bit tired is "tactical" and not "injury". Getting caught in your own lies makes you look foolish at best and cheats at worst. In this case I'm calling the latter............The logic behind that seems quite sound, you don't want to risk a player coming back from injury. However, However, the letter of the law says injured and not 'possibly could get injured'.
The worst I can see from this is, he tried to pull a fast one, the officials took a while sorting it out, the right thing happened and Leicester still lost?
Bloodgate actually happened, as in players actually did it and it wasn't picked up at the time, whereas here nothing came of it.
Ultimately, even if they had gone uncontested, Leicester would have had a guaranteed ball at the scrum and a two man overlap to exploit.
I also remember years ago, a certain team being smashed in the scrum and getting a front row to come off 'injured' and conventiently having no other front row replacements with about 20 minutes to go, so this isn't a new thing that Bristol have thought up.
So Lam is saying he's not techincally injured, but coming back from injury and to play him more may risk further injury.Lam said something along the lines of "If he goes back on and gets injured, it's on you" to the referee.
This then pretty much tallies with the previous statement.Lam's post-hoc rationalisation (player safety) was quite clever but utter horseshit.
This also tallies with the previous statements, it's a tactical sub because you don't want to risk an injury.Which was funny because resting an old fella because he's a bit tired is "tactical" and not "injury".
It is when you're subbed and it's either because the player can no longer play or because it was a tactical decision.Fitness however isn't a binary thing and recovery is a big part of it. If they'd genuinely deemed him good for only 40 minutes because they'd brought him back a week earlier than planned then they have a point not risk him coming back on. This doesn't fit into a binary 'injured' or 'not injured' situation, and officially he's not injured.