From: "David P. Reed" <dpreed@deepplum.com>
To: "Dave Taht" <dave.taht@gmail.com>
Cc: "bloat" <bloat@lists.bufferbloat.net>,
"cerowrt-devel" <cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] cringley rants well on bloat
Date: Tue, 9 Feb 2021 15:45:04 -0500 (EST) [thread overview]
Message-ID: <1612903504.690718796@apps.rackspace.com> (raw)
In-Reply-To: <CAA93jw6x26m9KD-wW97-Pbb2UbH2=xKnVOBFb9DXFEBQA5jkRQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2030 bytes --]
Hmmm... good post, I guess. But aren't WiFi 6 and StarLink being built by people who have proved their genius by being billionaires?
It's sad, though, to read through the comments. There's a whole 'nother world out there now.
Apparently the world of commenters are largely convinced bufferbloat doesn't exist, and never did.
Perhaps that is our problem? We are hallucinating and disconnected from reality?
I constantly hear that IETF attendees don't believe it is a problem. And folks like Andy Bechtolsheim get loads of VC money to create Ethernet 10+ GigE switches that are full of buffers, therefore creating lots of lag under load in datacenters where they buy this gear because Andy is famous. AndyB's company even produce white papers that claim more buffers improves performance by keeping all the links running at wirespeed (the hell with latency).
And some of the commenters seem to want to insult Jim Gettys, too, by name, saying that he "got it wrong".
I've concluded that COVID-19 reflects a general infection of brains with some kind of arrogant ignorance, including many of the folks who get boondoggles from their company to attend IETF.
But it may be the opposite, after all. Maybe we folks don't understand what is true in this real Bizarro World, and bufferbloat is a hoax like COVID. Q is probably right, and we are probably all pederasts like Hillary Clinton.
On Monday, February 8, 2021 8:45pm, "Dave Taht" <dave.taht@gmail.com> said:
> https://www.cringely.com/2021/02/04/2021-prediction-4-wifi-6-is-a-bust-for-now-as-bufferbloat-returns-thanks-to-isp-greed/
>
>
> --
> "For a successful technology, reality must take precedence over public
> relations, for Mother Nature cannot be fooled" - Richard Feynman
>
> dave@taht.net <Dave Täht> CTO, TekLibre, LLC Tel: 1-831-435-0729
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
>
[-- Attachment #2: Type: text/html, Size: 4018 bytes --]
next prev parent reply other threads:[~2021-02-09 20:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-09 1:45 Dave Taht
2021-02-09 20:45 ` David P. Reed [this message]
2021-02-11 17:12 ` [Cerowrt-devel] [Bloat] " Jonathan Foulkes
2021-02-11 17:44 ` Dave Taht
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/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1612903504.690718796@apps.rackspace.com \
--to=dpreed@deepplum.com \
--cc=bloat@lists.bufferbloat.net \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
/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