The vast majority of the time HTTP runs over TCP so there not exactly unrelated. Yes, most programmers tend to ignore things below a given level of abstraction, but that's hardly safe. However, you see the same thing on several different protocols and it was really just used as a simplified example.

Anyway, for a more detailed answer, DASH is more or less unrelated to the issue. A service that uses DASH and is willing to give clients a huge buffer which is filled up as soon as possible is going to have far fewer issues than a service that uses DASA and tiny buffers.

PS: For a real word example, having a tiny battery and recharging it three times a day vs once would save the company some manufacturing costs. A Roomba is automated so this might not seem like a big deal. But, while it might work most of the time just fine, it still significantly increase the risks it runs out of power.

In the end when watching a streaming service I have gigabytes of ram just sitting there... use them.