From: David Lang <david@lang.hm>
To: Sebastian Moeller <moeller0@gmx.de>
Cc: Michael Richardson <mcr@sandelman.ca>,
Dave Taht <dave.taht@gmail.com>,
Dave Taht via Bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] 80Mbit streaming
Date: Thu, 5 Oct 2023 22:26:23 -0700 (PDT) [thread overview]
Message-ID: <6n82r0q7-rnso-o93o-nnq0-1ns8185o92n8@ynat.uz> (raw)
In-Reply-To: <8F072AF6-D0B0-4ACC-9333-7CEB31CC9104@gmx.de>
On Fri, 6 Oct 2023, Sebastian Moeller via Bloat wrote:
> On 5 October 2023 21:53:55 CEST, Michael Richardson <mcr@sandelman.ca> wrote:
>> Sebastian Moeller via Bloat <bloat@lists.bufferbloat.net> wrote:
>> > Now finally, a use case that needs at least a ~100Mbps link... question
>> > is, how much better than the competitors streaming this is going to
>> > look?
>>
>> What's the point? My eyesight isn't actually that good :-)
>
> Mine neither... from my low-fi perspective, anything up to ~full hd (1920x1080) was a noticeable improvement, but e.g. going to 4K on a 43" screen does not feel any better...
> My comment was driven mostly by the observation that we are at a stage where (at the forefront of deployment) we make rates available far beyond what is necessary, e.g. in Switzerland xgspon which is marketed as up to 10 Gbps per user. The only things so far are 'more parallel' and 'faster downloads', so the 80 Mbps streaming is novel in a sense even though of arguable utility.
heh, back in college (mid 90's) my least favorite instructor (Advanced
Networking) class told us that there would soon be so much bandwidth available
that nobody would know what to do ith it and it would be up to us to invent new
uses.
that struck me as being extremely short sighted even then.
David Lang
next prev parent reply other threads:[~2023-10-06 5:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-05 17:04 Dave Taht
2023-10-05 18:31 ` Sebastian Moeller
2023-10-05 19:02 ` jf
2023-10-05 19:53 ` Michael Richardson
2023-10-06 5:07 ` Sebastian Moeller
2023-10-06 5:26 ` David Lang [this message]
2023-10-06 17:49 ` Michael Richardson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6n82r0q7-rnso-o93o-nnq0-1ns8185o92n8@ynat.uz \
--to=david@lang.hm \
--cc=bloat@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
--cc=mcr@sandelman.ca \
--cc=moeller0@gmx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox