Haha we're batting well but 300 feels like 220 with this bowling attack, and with dew likely to be an issue.Didnt even know Sreesanth was in the squad, so imagine seeing him in the lineup.
He's OK, but now India has 3 bowlers who can completely lose the plot (him, Praveen & Nehra) And no Harbhajan either and bowling with the dew.
So, what's a safe score? 500?
Yes played those two shots off Kallis very well. A couple of short ones off Steyn may be the acid test.Raina been working on the short ball? Looks much better, pulling and playing the uppercut.
You're not taking runs scored as a constant. If you don't do that your argument just amounts to "scoring more runs>scoring less runs". Sehwag faces significantly less balls than Dravid does, giving his opponent more time to win the game. Keeping total runs scored as a constant, a low strike rate would have been preferable for all of South Africa's batsmen in the match just past.Uppercut and Prince, give me a situation where a player scoring at a lower strike rate is actually better in test cricket. Not that it's not worse, give me a situation where it is better.
Again, I stress, strike rate is not the same as deliveries faced. Sehwag and other batsmen that score quickly also face a lot of deliveries. Just because they are scoring more runs off those deliveries does not mean that they are giving their team a higher chance of losing by leaving more time for the other team to win. There is the same amount of time taken up (more actually considering the boundary balls) and yet their team has no runs.
With all due respect, can't see how your argument has any merit, and IMO is just an overreaction to counter people who put too much emphasis on SR when judging a batsman. Yes its far from everything, but don't try and pretend that a good strike rate can be a negative.