What would you say those reasons are though? I think they mostly boil down to cost.
I agree with the article, but mostly for a reason the article didn't press on: performance and responsiveness. Making loads of small requests sucks, and on a mobile, it sucks times ten. HTTP/2 and whatnot have improved things but when you have even a small dependency tree of data, you can't avoid the network latency and it can quickly add up to a second or more of unresponsiveness.
Obviously this doesn't apply (or matter) in some circumstances, but in many applications I think it's worth the extra cost.
What would you say those reasons are though? I think they mostly boil down to cost.
I agree with the article, but mostly for a reason the article didn't press on: performance and responsiveness. Making loads of small requests sucks, and on a mobile, it sucks times ten. HTTP/2 and whatnot have improved things but when you have even a small dependency tree of data, you can't avoid the network latency and it can quickly add up to a second or more of unresponsiveness.
Obviously this doesn't apply (or matter) in some circumstances, but in many applications I think it's worth the extra cost.