From: Dave Taht <dave.taht@gmail.com>
To: bloat <bloat@lists.bufferbloat.net>, cerowrt-devel@lists.bufferbloat.net
Subject: [Bloat] building a better toaster
Date: Sat, 30 Jun 2018 11:28:05 -0400 [thread overview]
Message-ID: <CAA93jw4tmF2ESPE4VHwFqZG5RoyZc6m+6pcPcfcwQdSk3iKtqQ@mail.gmail.com> (raw)
There are some lessons here for getting anti-bufferbloat fixes into
std hardware.
http://esr.ibiblio.org/?p=8063
One thought, though, if you look at the (oft hysterical) comment
thread - if you make your point loud enough, toaster experts will come
out of the woodwork to help.
"[dualit]s don’t use springs–you lift the toast by hand–and they use a
mechanical timer. It’s like someone made a list of all the toaster
parts that break, then designed a toaster that contains none of them."
If only we could apply more of these design principles to the internet.
--
Dave Täht
CEO, TekLibre, LLC
http://www.teklibre.com
Tel: 1-669-226-2619
next reply other threads:[~2018-06-30 15:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-30 15:28 Dave Taht [this message]
2018-06-30 17:36 ` Jonathan Morton
2018-07-01 23:34 ` David Collier-Brown
2018-07-02 0:17 ` Jonathan Morton
2018-07-02 1:36 ` David Collier-Brown
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=CAA93jw4tmF2ESPE4VHwFqZG5RoyZc6m+6pcPcfcwQdSk3iKtqQ@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=cerowrt-devel@lists.bufferbloat.net \
/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