I don't mind being blown out inside 36 overs; that can happen in these slog feast era. This is the reason why ODI is so boring these days - you are out of the game, within few overs. Teams start slogging from ball 1, targeting 350 - in that process, you lose 2/3 early wickets - what happened to SRL A yesterday or today PAK A, exactly things 'll repeat. But, if the slogging works, chasing 350, the opposite happens most times - 3 down for 60 in side 10 overs & then rest of the match is statistical exercise. This happens, when the balance of the game is distorted artificially - smaller grounds, batting belters, mallets instead of bat, free hits ....
Today, I don't blame PAK A bowling much - ENG A did exactly what a team with batting depth would do if the target is in sight - blast after couple of initial overs. This guy middled everything, so it became embarrassment; even 3/4 early wickets won't have won this match for PAK A.
But, this is very much typical PAK ODI team's performance - clueless. One batsman hitting 125 at 125 SR, still being all-out 7 overs (I know PAK A batted for 46 overs) before schedule is a crime. There was no partnerships & I am sure at least 3 or 4 wickets went down right after a boundary & there was a criminal offence - last recognised batsman being run-out (no TV reply, so it must be decisive enough for open eye, which indicates a misjudgement or mix-up). It ended up like ENG A would have chased 344; but, I think anything close to 300, it would have been a different ball game& PAK A had the chance to post that, even from 44/3 - just didn't plan accordingly. It's a shame that, one top order remained not out at one end & 6 wickets went down from other end for ~50 with 4 overs still to be bowled.
Poor performance, pathetic planning. And, I am sure Basit Ali didn't notice that, ENG A, had to bowl 3 of those 4 overs by a pair of bowlers who went for 1/125 in 17 Overs. LO cricket is not PAK team, in current environment - too dumb, outdated, obsolete & clue less.
Sorry for the harsh words.