Totally agree with this. Ok we have performed above expectation but you would think India will still win the series so bedding in some players at home is a good idea. Need to get rid of Yuvraj first though. Be a good idea to remove both though.I definitely think this is a good time to drop Tendulkar (we are due to announce the team for next 2 tests, aren't we?). The younger batsmen have responded well, and in home matches, now is the time to allow them to build some confidence.
FixedTendulkar can't play![]()
Nah, this is bull****.in fact, Dravid was a passenger in the Indian team for several years prior to that England tour.
And who should have have been replaced with? Kaif? Yuvraj? This is your problem.He should have been dropped back then. He was a liability in the side. I care about winning. And if he wanted to come back, he should have played FC cricket, scored runs, and he'd be picked again. Ganguly left and came back. Unlike a lot of other people in cricket, I don't really hold people's age against them.
Again, yes it does. You don't drop a player because they aren't a 57 average player anymore. You drop them if they are not one of your best 6 batsman. Right now Yuvraj is batting like **** PLUS he is not test class. Sachin, for all his crapness in this test, scored more than Yuvraj did.And just because Yuvraj also isn't Test class doesn't mean Sachin shouldn't be dropped.
No it's not, Dravid was struggling badly since the start of the Aussie tour 08 (the one IN Australia), he made the odd century here and there on easy batting wickets but for the most part he wasn't doing nearly as well as most other batsmen during 08-011 (till the end of SA tour).Nah, this is bull****.
Yea, you do pick the six guys most likely to score runs. I'd back Rohit/Badrinath/Whoever to average more than 24 or whatever Sachin is averaging this year.Again, yes it does. You don't drop a player because they aren't a 57 average player anymore. You drop them if they are not one of your best 6 batsman. Right now Yuvraj is batting like **** PLUS he is not test class. Sachin, for all his crapness in this test, scored more than Yuvraj did.
So if you replace Yuvraj with Rahane, who do you think should replace Sachin? I'm a Rohit fan, but are you telling me he is a better bet to win India the next test? (since that is what you are getting at, you're not talking building the future, you're talking win the next test). Same goes for Mukund, do you think he is more likely to win the next test than Sachin?
The fact you think Sachin should have been dropped in 06 and have refused to admit you were wrong is ridiculous frankly.
When? Name the period, name the tests, and name who you would have replaced him with.Frankly, he was a passenger in the side for far too long and other players could have done better.
You're taking your philosophy to the extreme though.As for dropping - if you don't perform, you need to be dropped. If you score runs again, you should be picked again! It's really that simple. Frankly, he was a passenger in the side for far too long and other players could have done better. If he had found his form again in FC cricket, I'd have no problem with immediately putting him into the team again. I don't see why anything except performance should be the criteria for selection. Obviously, you don't want to drop someone after a couple Test matches, but I don't believe in sacrificing the next Test match in order to potentially win one a year from now.
Well no ****. If I include his whole career, he averages 50+ and I'd pick him for the next ten years. We're talking about stretches of being in form vs out of form.^ Ahaha... you left out Sachin's 241* vs Aus and 194 vs Pak during the start of 2004, how convenient.