Spikey
Request Your Custom Title Now!
nah not really. most byes are the result of a wild ball that wasn't called wide, or in the case by some balls by spinners, were pretty much impossible to stop.Would be nice to see Keeper's bye conceded.
nah not really. most byes are the result of a wild ball that wasn't called wide, or in the case by some balls by spinners, were pretty much impossible to stop.Would be nice to see Keeper's bye conceded.
In no way shape or form is that true, and you've just underlined the problem what is wrong with people who use conventional stats.Meh.
Runs per dismissal, for batsmen and for bowlers. Tediously under-rated by sneery "I'm too good for stats" merchants.
Even though it never tells the whole story a batting average or bowling average will almost always tell you far more than any other stat. Because cricket is about scoring more runs than the opposition, and averages go to the heart of the matter for both bowlers and batsmen.
Yeah pretty much. Would be more useful to use a +/- for keepers.nah not really. most byes are the result of a wild ball that wasn't called wide, or in the case by some balls by spinners, were pretty much impossible to stop.
It tells you a little bit about consistency but average+standard dev tells you a lot more.Ummm because it shows how consistent the batsmen is?
Surely that is obvious. Not sure how someone can possibly not see that.
Yeah, I'm thinking along these lines too.Wouldn't mind an equivalent of WAR for cricket though I think it would be particularly hard to implement due to the relative lack of cricket compared to Baseball. Is there a way to check the percentage of someone's runs come from "extra base hits" or whatever as a rating/percentage of runs scored from anything more than ones and twos.
Hmmm. Has anyone done this here?It tells you a little bit about consistency but average+standard dev tells you a lot more.
I'll ignore the shriller aspects of that post and just say this. There is a whole constellation of statistics that can be considered to attempt a rounded analysis of a player's contribution and ability. But ultimately the boring old analysis remains: which team's players score the most runs per wicket? And that means that, imperfect though they may be, the batting average and bowling average are the two key statistics.In no way shape or form is that true, and you've just underlined the problem what is wrong with people who use conventional stats.
The line 'because cricket is about scoring more runs than the opposition' sums it up how ignorant it is to say these stats are the best. The team with the most runs does win cricket, but there's more to cricket than just individual scores. It's a team game built upon partnerships and maximising your teams score, not your own. So frustrating that people have such a sheltered view of how cricket is played.
Ditto to this. Seems flawed to compare two bowlers' economy rates when one might regularly bowl at the death or in the power-plays, when another only gets used in the middle overs with 5 on the boundary.I'd like to see a stat for bowlers in ODIs, which breaks down their E/Rs at different stages of the 50-over innings. I.e. the first 10 overs, the middle, and the last 10 overs.
Kyle Mill's figures would be astonishing good for overs 1-10 and beyond dire for the death overs.
Thankyou. Certainly a better indicator than benchmark's eyes ffs.Meh.
Runs per dismissal, for batsmen and for bowlers. Tediously under-rated by sneery "I'm too good for stats" merchants.
Even though it never tells the whole story a batting average or bowling average will almost always tell you far more than any other stat. Because cricket is about scoring more runs than the opposition, and averages go to the heart of the matter for both bowlers and batsmen.
Strange post.I'll ignore the shriller aspects of that post and just say this. There is a whole constellation of statistics that can be considered to attempt a rounded analysis of a player's contribution and ability. But ultimately the boring old analysis remains: which team's players score the most runs per wicket? And that means that, imperfect though they may be, the batting average and bowling average are the two key statistics.
Compared with batting average a statistic such as, for example, scoring shots per balls faced (however useful that might be as a coaching tool) really is quite unimportant.
Thilan Samaraweera is better than Viv Richards.Thankyou. Certainly a better indicator than benchmark's eyes ffs.
You got beef with Samaraweera?Strange post.
Since when has the team with the best runs per wicket ratio automatically won the match?
Since when has 54* and 40 been more valuable to the team than two scores of 80's??
Never mind the fact that you've totally missed the point of balls scored off as a statistic. Noone has advocated that replacing average. It's better than strike rate though.
Strange, strange post.
Thilan Samaraweera is better than Viv Richards.
MY STATS ARE BETTER THAN YOUR EYE!!!
That's a pretty useful one.Not sure if it has been mentioned yet (CBF reading all of your thread, Benchy, you ****ing ****), but I'd like to see a stat for bowlers in ODIs, which breaks down their E/Rs at different stages of the 50-over innings. I.e. the first 10 overs, the middle, and the last 10 overs.
Kyle Mill's figures would be astonishing good for overs 1-10 and beyond dire for the death overs.
Straw man. Yawn.Strange post.
Since when has the team with the best runs per wicket ratio automatically won the match?