this argument does not make a ton of sense to me. would it be better if they were charging by the byte? that's fixed and you can measure/control how many bytes you send, but you still have little control over how many bytes you receive, or whether those bytes are useful in the first place.
likewise, suppose you buy a 1gb plan from a mobile isp, then you find a youtube tutorial that you're interested in. the nugget of information you need is 23 minutes in, but you have no way of knowing that upfront, it may not even be there. you can exert some control over how many bytes you send in the headers of the get requests to youtube, but you have little control over how youtube compresses the video you requested. also you download 2 30s ads and a sponsored segment before finding what you were looking for. unfortunately you're now out of data on your plan. do you blame your isp for their shady sales practices? is it youtube's fault? what did you pay for?
likewise, suppose you buy a 1gb plan from a mobile isp, then you find a youtube tutorial that you're interested in. the nugget of information you need is 23 minutes in, but you have no way of knowing that upfront, it may not even be there. you can exert some control over how many bytes you send in the headers of the get requests to youtube, but you have little control over how youtube compresses the video you requested. also you download 2 30s ads and a sponsored segment before finding what you were looking for. unfortunately you're now out of data on your plan. do you blame your isp for their shady sales practices? is it youtube's fault? what did you pay for?