Mister Wright said:
Whether a batsman is caught or dropped has no bearing on his ability. Just say a batsman creams one off the middle of the bat , it's sailing for six and suddenly a fielder comes out of nowhere and pulls in a remarkable catch, does that mean the batsman has less ability than someone who top-edges one over the keeper's head for six? I think not. And if in that same situation the fielder drops what would have been a remarkable catch, does that mean that the batsman has less ability either?
You've mentioned many times that it is the object of the batsman to score runs without getting out, that is true, so does that mean a bowler who goes for one run in their innings has no ability? Because afterall it is the object of the bowler to go for less runs.
I find that last paragraph a little confusing. Do you mean "does that mean a bowler who goes for one run in their innings has lots of ability?"?
I will assume you do.
In the one-day game it is the object of the bowler to go for as few runs as he can. Therefore if he bowls 10 overs for 1 run, yes, he's bowled exceptionally well.
In the First-Class game it's a bit different, as the object of the game is not to concede as few runs as you can off as many overs as you can bowl, it's to take as many wickets for as few runs (well, except in exceptional circumstances, like last-session run-chases). So, even if someone bowls 10 overs for 1 run in a First-Class game, it's still not a spell that's fulfilling your ultimate objective. It's a pretty good spell, clearly, but not one that's fulfilling the objective.
Quite what it has to do with the question of chanceless run-scoring I don't know, but I hope I've answered what you were asking me.
Regarding the other question, if someone hits the ball in the air and a fielder suddenly learns to fly and catches something that would have gone for six clearly the batsman is rather unfortunate. If someone hits the ball in the air and a fielder catches it, whether it would have gone for six or not, you would still expect that catch to be taken.
A top-edge over the wicketkeeper's head, meanwhile, isn't a good stroke, but it's still good enough not to get out, because you've hit the ball away from the fielders.
If you're seeking faultless batting you're never going to be satisfied, unless you can find a ball-by-ball video of Bradman's 254 at Lord's in 1930.
I have always said you must be realistic about what you call a chance. If someone has a catch taken which, frankly, had no right to be taken, then that should be remembered, eg Trescothick-Arnold-Hettiarachchi at The SSC in 2000\01. There is such thing as a lucky catch.
Similarly, there is such thing as a let-off and generally it's possible to get near-universal agreement on what should and shouldn't have been out.
If you are dropped, you are lucky. If you are missed stumped or given not-out when you should be out, you are lucky. If you get given out when you shouldn't have been, or caught when the catch didn't bear anything to the ability of the fielder, then you're unlucky. If you get a realistically unplayable delivery, you're unlucky.
And so it goes on. Only some things are included in the first-chance average. But others should be equally remembered.
If you are not out when, under normal circumstances, you would be out, of course it reflects on your ability.
Because I stand by the statement that the ability in batting is scoring runs without getting out. If you get out, you can't score runs. If you do something which would normally result in your dismissal but, for whatever reason, doesn't, you don't deserve credit as if you had avoided it.
I also ask yet again, the question: what is the difference, as far as the batsman's ability is concerned, between a dropped catch and a caught catch?