The Ashes: RavBopping
Since the 2nd Test reached it’s conclusion, there has been a concensus in the press that goes as follows:
Ravi Bopara hasn’t scored any centuries against Australia yet, so clearly batting at number three is too much for him. Shane Warne must have been right about him after all.
This trend shall be known as “RavBopping”. Apparantly, four innings are ample time in which to condemn a young player who had previously scored 3 consecutive Test centuries. It is acceptable to do this because those centuries were “only” scored against the West Indies. The saving grace is that there haven’t been any calls to replace him in the team alltogether. But it surely won’t be long.
In this high-octane world, everybody wants everything, and they want it right now. And, if they don’t get it right now, people start to jump up and down, scream and wave their arms about like Monty Panesar appealing for a bat-pad.
So, here is the voice of reason:
Two average Test matches are not sufficient time to decide that Ravi isn’t up to the job. Every player has experienced two consecutive average Test matches, even Don Bradman. I know, I have checked. When he gets to, say, 10 matches it will be time to address the situation. By which time, the press will be calling for poor Ravi to be thrown off the end of Southend pier.
Ravi Bopara will bat at 3 for England at Edgbaston. For any who don’t pay much attention to the England selectors and their recent track record, let me remind you that they don’t like to change things about very much.
Comments:
0